I did something similar when updating for RC4. I stopped the two masternodes messed up together, tried again 24h later and everything went fine.I just terminated one of my masternode servers and launched a new one but it was given some of the same IP addresses and now I have duplicate entries in the masternode list. How long until they disappear? It looks a mess!
1. Not sure, but I'd say yes until enforcement?I won't have access to my cold wallets for the next 8 days or so.
- I do nothing, local/remote darkcoind stay at RC4. Do I get coins or not?
- The remote wallet is updated to RC5, local wallet not. Is it dangerous to update the local wallet later when I have access to it again?
- Evan is hit by a bus and no one can answer my question?
- There are just 4 questions. Why did I write 5?
I just terminated one of my masternode servers and launched a new one but it was given some of the same IP addresses and now I have duplicate entries in the masternode list. How long until they disappear? It looks a mess!
v15 is just for removing that debugging button. Everything else on the network is looking good. -Evan.Hey guys, what is actually the difference between the RC5 .14 and the .15 build? There's currently no information about that on github. Is an update from RC5 .14 to RC5 .15 mandatory?
Anybody know why
darkcoind masternode list | grep <MN IP>
Would not be working on the remote MN server?
It started before RC5 update
I started a 100DRK in 4 Rounds with 80DRK in the WIN Qt at 17:35 EST
Only 50% completed now 20:59 EST
I first sent all coins to myself - to a new addy
Anybody else experiencing anything like this?
If you are running a cold/remote setup, you don't need to send the coins to a new address because your config file with the setting masternode=1 disabled darksend at startup (no need to worry about 100 vs 1000 keypool). When you want to actually send your coins, you would send a fresh wallet generated in RC5.Hi,
Do I need to generate a brand new wallet?
Is that as simple as moving the wallet.dat out, creating a new one, then swapping them to send funds from old to new? Won't that screw up the remote masternode?