Wallet empty after multiple crashes

I was asking for the exact location, because that would make talking about it easier. :slightly_smiling_face:. So, all right, the C: drive it is.

You can use any location, so select the folder you want to use. It can be C:/Reddcoin or C:/Crypto/Blockchain/Reddcoin, whatever your like. This will be your “Reddcoin data folder”.

Regarding the wallet.dat file, you need a fully blockchain for that, so I would propose this:

  • Select your Reddcoin data folder.

  • Reddcoin will start syncing. Let it sync, do not bootstrap.

  • When syncing finishes, exit Reddcoin Core. Go to your Reddcoin data folder. Rename the existing wallet.dat, and copy your backup wallet.dat to that folder.

  • Start Reddcoin Core. You should have the correct/expected balance.

I followed the instructions yesterday afternoon. Started a new Reddcoin core. It came up with no balance and no transactions (both expected). It reported “Synchronizing with network…” and 6 years and 26 years behind. This morning it remains the same. There has been no progress toward becoming synchronized.

Help screen says I’m on Reddcoin Core version v3.10.2.0-25f95e5-beta (64-bit)

  • Ed

I’ve done a fresh install of Windows 10, and also installed Reddcoin Core. Have the same issue as you.
A restart of the wallet software seems to help, until it stops syncing again.

I am using a VPN connection, but that didn’t matter before… Are you using a VPN by any chance?

I will contact the devs about this, and will keep you posted. If you don’t want to wait, you can try restarting the wallet software (exit/close, and start again) to see if that helps, in the mean time. Otherwise, you can also try bootstrapping…

In my debug log I see a lot of orphan blocks, that might be the issue…

The reply I have received:

the v2 nodes are causing some disruption still
Try restarting wallet, and when the blockchain starts syncing past the following into the console

copy and paste this into the console

setban 71.92.100.122 add 1640908800
setban 71.91.191.45 add 1640908800
setban 98.222.228.88 add 1640908800
setban 84.25.124.43 add 1640908800
setban 178.254.9.98 add 1640908800
setban 92.242.3.82 add 1640908800
setban 207.172.89.90 add 1640908800
setban 85.255.234.198 add 1640908800
setban 98.1.33.204 add 1640908800
setban 211.46.5.49 add 1640908800
setban 184.22.118.3 add 1640908800
setban 89.244.160.103 add 1640908800
setban 99.55.161.73 add 1640908800
setban 82.73.63.84 add 1640908800
setban 178.69.193.254 add 1640908800
setban 115.213.93.220 add 1640908800
setban 109.62.228.162 add 1640908800
setban 203.213.102.23 add 1640908800

these are a bunch of nodes i have seen on v2

 

Restart Reddcoin Core (exit/close, and then open/run).

Open the Console tab via Help → Debug window.

In the Console, enter the setban commands from above; one by one.

Let me know if this makes any difference.

This morning, on a whim, I rebooted my desktop, renamed the Reddcoin folder and downloaded a new executable. It installed as expected and when it started the Reddcoin core, it said it was starting 6 years and 28 weeks ago. The window on the bottom of the screen then went to 6 years and 27 weeks behind. Then 6 years and 26 weeks behind. All in a few seconds. Then it remained on 6 years and 26 weeks behind. After 5 minutes, it went to 25 weeks behind. It is now at 24 weeks behind and seems to be progressing toward syncing up to date. Just before sending this, a pulsing green temperature bar appeared on the left side of the window reporting the progress, now at 23 weeks.
It looks promising.

  • Ed

Great!

For your information, I also received this info from the devs:

some improvements coming for peer management
within the wallet, the peers tab now has a context menu where you can right click and select a time period to ban for
additionally, the list of banned peers are displayed, where you can also select to unban.
bonus points, the banned peers are now saved and loaded from the filesystem

https://i.imgur.com/NXCFTbz.png

for the orphan block issue that some are experiencing,
This will be fully resolved with the switch to headers-first synchronisation (no more orphan blocks allowed during sync)

The above should be in our next release (3.10.3).

Yesterday it got to 6 years and 1 week and seemed to stick there. The temp bar stopped pulsing, it was steady. I did a back up of Reddcoin, closed down the core and rebooted the desktop. When I started up Reddcoin, it came up “Synchronizing with network…”, 6 years and 1 week behind, and the temp bar was pulsing. In a few minutes, it said 6 years and 0 weeks behind.
I’m not sure why this happened, but I tried something and wanted to report the results. My plan going forward, is this: if the temperature bar stops pulsing, I’ll shut down the app, reboot the computer and start up again.
As I write this, it is now 5 years and 51 weeks.

Today, Reddcoin seemed stuck on 2 years 31 weeks. The green temp line was not pulsing. I backed up, and restarted, without a reboot of the computer. It came up with the green temp line pulsing. It is now 2 years 30 weeks. We seem to be making progress.

Have you tried the setban commands from a few posts back?

Thanks for your patience…

The upcoming version (v3.10.3) should solve the syncing issues as mentioned before.

This morning the app appeared fully synchronized, as there was no message about being out of date. It had no balance and no recent transactions. When I went to settings, there was no option to unlock. I made a backup, closed it down, copied the last backup that had the full balance into the data directory. I started it up again. When it loaded, it opened up with the balance of 8/2 , no stake or pending, and a record of transactions through 8/5. The 8/5 transaction was dimmed and wasn’t included in the balance. I keep a record of balances. The other listed transactions (assumed to be in the listed balance) were not dimmed. I made a backup and drafted this report.

Today there is a new transaction entry for 8/16 so apparently staking is happening. Curiously, the entry for 8/5 is still dimmed while the entry for 8/16 is not. I cannot resolve any of the additions with the totals I have recorded. I would guess that, for some reason, the transaction for 8/5 is not included. Do you think it might be included if I did a “rescan” as was done in the past?

  • Ed

Yeah, you can always try a rescan; don’t forget to backup first (just in case…).

What is the difference in balance your missing?

About that transaction of 5 Aug, what do you see in its transaction details (double click it).

The balance on 8/5 that is dimmed in the listing of transactions is 556.1405 RDD. In the details, it says the Credit is 328.5599 RDD and the Net Amount is the same. Don’t understand why they would be different amounts or where the difference went.
The details say it is generated but not accepted. “Generated coins must mature 50 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to “not accepted” and it won’t be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.”
Based on that, I’ll just leave this as it is. I don’t believe a “rescan” will accomplish anything.
Thanks for the guidance on this.

  • Ed

Generated but not accepted happens with stake rewards. It means that somebody got that stake reward as you on the same time, but your internet connection was flaky/not reliable, so it got confirmed/accepted for them, but not for you.

As far as I know, it only happens when the internet connection is not stable. I would advise to use a wired connection (ethernet) if possible.

So, the amount of that transaction (generated but not accepted) is not added to your balance. But no worries, as your coin age has not been reset, you will just receive the amount with the next stake.

Thank you for the explanation.

  • Ed