Quote from: bumbacoin on April 06, 2017, 02:00:32 AM

Quote from: happycamper89 on April 05, 2017, 04:11:02 PM

Quote from: bumbacoin on April 04, 2017, 10:46:16 AM

Quote from: happycamper89 on April 04, 2017, 08:38:05 AM

Yes I went into File, Backup Wallet .., saved the .dat file and then replaced the current .dat file with a previous auto-saved.dat file. I received an error message about the client not being found and the wallet crashed. I restarted the wallet with a zero balance although the block chain was still synced. I cannot access the private keys now. I may have just burned a masternode.

why cant you acccess the private keys now?

have you tried different wallet backups?

Its because now I have a different wallet entirely it seems. if I request a dumpprivkey on the console, I get this message: Private key for address EaAi5DsnT7Qmo2NEWQP7nweNPowTqnZmmj is not known (code -4). but I didn't do that before replacing the .dat file before so I think I lost my old wallet with all the coins. Damn.

Question: In your guide you say to enter rpcallowip=127.*.*.*:* into the .conf file. Is that is supposed to be replaced with my specific ip address found through getpeerinfo?

oooo, does sound bad :p
there are 10 automatically created backups in my exclusivecoin/backups folder, do you have other ones to try? i assume that every time i start up it replaces the oldest one so make a backup of them all might be a good idea.

rpcallowip=127.*.*.*:*
is to allow local rpc connections such as miners for PoW, it is not actually necessary for the masternodes.

Yes that was a costly mistake and I will definitely be more cautious from now on. That's one way to create scarcity I guess. I have 5000 more coins so I am starting the node and just needed that clarification on the .config file instructions- thanks!