Search results

I would vote yes just to reduce the miner reward but I find this proposal disappointing and frankly misguided. We should target the miner reward based on the amount of security we need. And equally we should target the MN ROI based on the number of master nodes the network needs. Using the...

I'm not aware of any history of camosoul so I didn't have that context. Thanks for reaching out in private to offer help with my MN. All good. Sorry if I offended anyone. Have a nice day!

camosoul was complaining about software in general. Same. It was pretty clear that camosoul was stressed about all "his" nodes going down. Sure he should have been more polite but suggesting that he write documentation for any project was not helpful at all. I'm sorry I missed that that was...

https://www.dash.org/forum/threads/dash-core-v0-14-on-mainnet.45821/page-3#post-212534

The masternodes exist to serve the network but let's not forget that DCG exists to serve the MNOs. When someone is having trouble with the software provided by DCG, it doesn't make sense to expect them to write the documentation for it that they themselves so desperately need. And it's...

2 GB has been running fine for me so far.

How did you contact him? I've been trying to contact him for months, through both email and discord. I've stopped using the service but since there's no way to pay him, there's no way to stop paying either.

@moocowmoo has been unresponsive for months and masternode.me is losing nodes to PoSe bans. Maybe masternode.me should be removed from that list?

I thought DIP8 = chain locks?

That's 4033 blocks. If the first window started at 1,076,544, then the second window must also start at an even number, otherwise you have a window with odd size. I'm not sure what is the exact cut off, but I assumed every window start with an odd number since I assume the first block was #1...

For DIP8 to activate we need 80% of blocks between 1080577 and 1084608 to be signaling support. That's 3226 blocks or more. Block 1084340 was the 3226th block since 1080577 to signal so DIP8 is now guaranteed to be locked in and will active at 1088640. Since is expected to happen (with 90%...

@JGCMiner I guess an additional cause for PoSe banning was introduced recently, but my node was PoSe banned in April after I changed the operator key, so PoSe banning definitely existed. If you think it's off topic here, I'd appreciate an answer on the other thread.

@flare I also had a MN banned once when I changed the operator key (thread). Could you explain the point of being able to change the operator key (using protx update_registrar) if it will get you banned anyway?

This sounds concerning. Is anyone at DCG aware of this yet? FWIW, my node doesn't run on Amazon and is still at 0 PoSe score.

Isn't 80% miner signaling also a condition for the sprok? And to answer my own question from earlier, I'm guessing that the signaling can be seen as version 0x20000010 instead of 0x20000000.

How can I see if a specific block is voting for activation? If I look at Blockchair, all blocks only seem to be voting for BIP9.

Same for me. I didn't move my collateral so this doesn't make sense. I already commented on the badge thread but didn't get any response. https://www.dash.org/forum/threads/new-forum-feature-masternode-owner-badges.13819/page-2

Where/how can I track miner adoption/signaling?

I'm rather disappointed with Fernando's answer to my question. Resetting the votes was an engineering shortcut. It may be understandable that people think this would be fine, but suggesting that it was unavoidable is rather dubious. I think in hindsight the responsible thing to do was to support...

I seem to have lost my MNO badge, even though I didn't move my collateral.