I am trying to understand the state of an old Bitcoin Core wallet synchronization / rescan.
Context:
- Wallet type: old legacy / non-HD wallet.dat, likely created around 2009–2011
- Machine: dedicated MacBook Pro 2022/2023
- Bitcoin Core runs 24/7
- Sleep is disabled via: sudo pmset -a disablesleep 1
- The machine is used only for Bitcoin Core
- Internet connection is stable LAN / fiber
- Current GUI progress: about 96.21%
- First documented progress: 94.46% on 2023-11-19
- Important later points:
- 2025-12-21: 96.00%
- 2026-01-15: 96.04%
- 2026-02-27: 96.10%
- 2026-04-17: 96.17%
- current: 96.21%
- The data directory is around 80 GB
- The GUI currently shows 0.00000000 BTC
- I was told there may be many keys in the wallet keypool, possibly hundreds or thousands
- I was also told that around 36,612 blocks may still be open / unprocessed
In debug.log I repeatedly see lines like:
UpdateTip … progress=1.000000
I also see several lines like:
[net:warning] pcp: Could not receive response: Connection refused (61)
I do NOT see obvious errors such as:
- corrupt
- database error
- wallet.dat corrupt
- cannot rescan beyond pruned height
- reindex required
My questions:
Old legacy/non-HD wallet.dat: Bitcoin Core has been extremely slow since 2023. The GUI is currently at 96.21%, the wallet shows 0 BTC, and debug.log repeatedly shows UpdateTip ... progress=1.000000 with no visible DB/corruption errors.
Does this indicate a normal but very slow wallet rescan/DB bottleneck after completed IBD, or does it suggest a configuration/problem state?
thank you in advance!
