Masternode Update

There's a few possible reasons that some of you are getting delisted.

1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)

To figure out which one you are:

1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.

You can also also try 10.16.7 (this version will ONLY connect to new peers):

Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind

Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip

This is the same type of calmness we saw before the last run up!

MNs out after an hour after deleting peers.dat local and remote

getpeerinfo gave me new peers only

will check 10.16.7 now

after ./darkoind masternode start I get 'masternode started remotly' but I am not at the masternode list. strange 

I get paid while I was online btw