Search results

When enforcement is switched on, there will be forks, which is what the network is supposed to do: fork off the unknown pools. :)

I think the MN processing a transaction is randomly chosen, whereas the MN reward is paid using a 6 vote system. So, I can't assume the stacked MN has a greater probability of processing a transaction, though it has greater probability of winning the MN reward. I don't know if people would like...

Also please see AlexGR suggestion that high resourced people can do their own stack in one MN via virtual servers on the one machine. i.e. There is no need to mess with the protocol to allow multi ticket on one MN. https://bitcointalk.org/index.php?topic=421615.msg7046010#msg7046010

You should be closing ALL ports other than 9999 on your MN. Using CSF to do that is so easy. Leaving an open SSH port even if port number is changed is asking for trouble. That's what happened to Reda.

Well, my guide is an improvement on what the original guide provided, so I'm not sure what you mean?

Thanks for all the hardwork Evan. Do realise how difficult this must be. I have two questions: 1. If there is no way for pools to hardcode/set which MN they vote for - why are 6 "votes" required? 2. Re: auto checkpointing - is this for MNs only or for the entire network of nodes?

Did anybody have issues with wallet.dat not being recognised by masternode? i.e. ./darkcoind masternode start secretpass Receive message: not capable masternode I substituted wallet.dat with a test wallet I created and the masternode works fine. Any ideas guys? BTW, here is a dummies guide to...

Had interesting issue today. Did all the steps. Installed wallet.dat - created by my friend's Win8 machine using 9.4.11 wallet. Got incapable masternode. Checked balance - 1000 darks exists in one wallet address. He tried creating another wallet.dat using 10.8.11. Also incapable masternode...

Thanks. Worked it out. :smile:

Any replies to this?