Will there be a limit to how many masternodes can be run in one instance? I can't help but think it just makes it easier for someone to track what's going on (if a loop hole were found)
You still need unique remote instances for each masternode. This just allows all the local wallets and configs to be in one file each instead of a pair for each masternode.Will there be a limit to how many masternodes can be run in one instance? I can't help but think it just makes it easier for someone to track what's going on (if a loop hole were found)
Will there be a limit to how many masternodes can be run in one instance? I can't help but think it just makes it easier for someone to track what's going on (if a loop hole were found)
Correct, "start-many" is just a convenience method. The architecture for masternodes does not change.You still need unique remote instances for each masternode. This just allows all the local wallets and configs to be in one file each instead of a pair for each masternode.
Thanks, Flare! When I get home, I will send you another DRK beer!Will migrate my masternodes to the new setup scheme and will capture all i did
Much easier, this WOULD be fantastic!This is fantastic news... will definitely be importing my priv keys into one wallet to manage one wallet and one config file when more information is released.
This needs warning message for sure.
Make a JIRA suggestion.
eta plz got drk kthxbiWill migrate my masternodes to the new setup scheme and will capture all i did
Words can't describe how happy I am right now...Yes, that's exactly the way it's working, there is now a 'masternode.conf' file with each line containing the masternode-n-addr and masternode-n-privkey.
Look at https://github.com/darkcoin/darkcoin/commit/f088a8f56d3908c140e2e92c65ac33c83783ade2 to get an idea of how it works
So to start 4 masternodes you'll need to have 4 addresses funded with 1000DRK in your wallet and the masternode.conf file containing 4 lines with masternodeaddr and masternodeprivkey for each MN - and then fire a "masternode start-many" command
Yeah, looking at blocks 155473, 155474, 155481, 155482.
They will. They've been prompt at updating when I've messaged them, however, they haven't been on BCT in days so probably haven't seen it.oblox just posted it some seconds before you )
we still need miningpoolhub to be dark
It seems like but my node was also getting not_detected payment once with 0.10.15.13. Also, it seems that we cannot trust the monitoring nodes on poolhash or drk.mn. But, when pool hash shows that my masternode is completely inactive, it often goes from 1 to 0 in the grep result. sv02 from poolhash has a nl status now.I am curious though why recent blocks found by suchpool and wafflepool are being paid to RC3 masternodes, unknown, or unpaid according to drk.mn even though they are on onyx.