I think you're right, the network seemed to be sorting itself out, but maybe Evan spotted something we didn't? I've noticed a minute or two of lag both locally and on my masternodes before, they all always catch up, no forks, no problems.
Also, in case anyone hasn't figured out how to update and restart their masternodes with the newfangled cold/remote setup, here is what worked for me:
On remote:
darkcoind stop
mv darkcoind darkcoind-old-version-number
wget
http://www.darkcoin.io/downloads/rc/darkcoindchmod 755 darkcoind
darkcoind
...wait for it to sync up if needed
On local:
Stop local client if running
Edit your darkcoin.conf and put back in:
masternode=1
masternodeprivkey=your-priv-key-for-that-masternode
masternodeaddr=x.x.x.x:9999
Rename your copy wallet for that masternode back to wallet.dat and fire up the local client or daemon
Wait for it to sync up if needed, then
masternode start 'your-wallet-passphrase'
- you should get 'masternode started sucessfully' and you can now take the local wallet offline again, your masternode should appear at
http://drk.poolhash.org/masternode.html within a minute or two.
This. +1000
Thank you for offering your solution in a thread that's supposed to be about DRK and not a pissing match between coins. I'm having problems with finding good instructions on upgrading from RC2 to 3 and implementing cold wallet storage.
I also couldn't implement the final command to start payments from the local wallet with coins in the local cold wallet. On the other 3 nodes I was setting up last night, I kept getting a local qt console error that the masternodes variable needed to be set to 1 in the conf file...of which, it was set correctly in both conf files. Configs looked good and matched 100% on both ends.
I just paused my set up of community owned MasterNodes until the situation with RC3 sorts itself out.