On testnet for this release (and maybe previous ones, I don't know, I always run a hot wallet on testnet) you have been (mostly) able to just swap in the new darkcoind, start it and that's it, the Masternode restarts itself without the 'masternode start' command being needed anywhere. Apparently this has been possible for some time on mainnet too, but I've always done the local restart thing.
As opposed to just updating the remote daemons and restarting. I found I had to issue masternode start from local for this one, although, I did get 1s from just the remote update (about 30 second downtime to update). I was going off the poolhash and drk.mn listings which made all my mn's show up as inactive but I figured afterwards it was due to them not being updated.
Yes, I think the Bit License is for the State of New York BUT since NYC is the financial center (Wall street etc.) of the US, it is likely that the other states will follow them.
Elbereth and El Presidente first need to update their nodes to reflect the current state.
You can send an Inbox message to them. But I am sure they already know. We just have to be patient and if it takes so many confirmations it won't show up on those sites anyway until the confirmations are done.
This has nothing to do with confirmations. The protocol version was changed. Older daemons are not able to receive the current masternode list.
You are almost right. To be selected for payments one needs "masternode count" confirmations. But to just start a masternode, 15 confirmations are sufficient.
Some people (with the update) already have their MNs showing up on those sites. At this point like flare said, give it 24 hours. Also this is a new protocol and it takes a lot of confirmations, not 6 anymore. We went over this on testnet. Evan needs to confirm this.
I just choose a randomly higher number then the current. I think i went with 70058 cause it allowed me to only change one character. LOL.
Why you did those crazy things with wallet.dat?
After successfully syncing new client, there's a new (EMPTY) wallet.dat in APPDATA folder. You only need replace this new wallet.dat by copying the old wallet.dat you saved in that Desktop folder. Hope this helps.
That is what I have been doing. My old wallet.dat file must have been overwritten, IDK. I have an even older wallet.dat file on a USB drive. I've tested both older wallet.dat files in new empty appdata folder and I still get same result. I'm sure it's user error, but I do update wallets for various coins often without to much of an issue. I appreciate the response.
