Hi flare chaeplin .
I've updated all my MN to New IP and New Prive key with version 10.11.5.
most of the MN are working smooth and perfect. but here is my problem:
one of my masternode with ip (xxx.xxx .xxx.166) which setup and running well (its old IP was xxx.xxx.xxx.198). but it showed on Presiden's Masternode list as 198. and it's 166 on elbzo.net.
i've repeat several time to setup this MN and everytime with new generated privkey. i'm preety sure all the operations are correct. and everytime i got the massage from both Local/Remot :successfully started masternode
So did i make some mistake or it's just cache problem? and the only thing is waiting? (i've waiting about 8 hours since MN setup.)
For me it's just a caching problem, whereas i can understand that this may cause a feeling of discomfort.
But regardless of what entry (198 or166) is in the lists: As long as either of them is in the list you should be fine.
Only way to get a cleanroom setup would be to
- get a new IP for hot masternode
- generate a new cold wallet.dat
- transfer 1000DRK to it
- generate new masternodeprivkey and copy to hot masternode
- start new masternode
That way no traces of old setup should be left in the masternodelist-cache thoughout the network.