I opened an old wallet and saw all my transactions there, everything looked good, but it took 14 hours just to rescan. The debug.log file showed the real story, the GUI was just stuck on a blue loading bar without any info. I closed it for a bit to open another wallet and it started rescanning from 0.49% for some reason. What gives?
Wallet Rescanning Issues After Closing
2 replies 434 views
You don’t really need to use the "Close Wallet" option every time before shutting down. If you do that, your wallet can miss new blocks during that time, leading to a longer rescan later on. But honestly, how come it takes so long to rescan something you just closed? It should only need to check a block or two, right? In debug.log, it should show you where it resumes from.
gwei_blockNewbie
Posts: 185 · Reputation: 37
#3Jan 4, 2021, 05:10 AM
Quick thought: does OP have txindex=1 and blockfilterindex=1 in bitcoin.conf? That can really speed up rescanning with newer Bitcoin Core versions. I remember you saying you’re using Knots, hope that works too! I’ve got like 8 wallets open, some are watch-only, and they all load super fast for me. No need to close them at all.
Related topics
- Wallet Issues After Editing.dat File, Need Help! 19
- Do derivative traders move funds to wallets after closing positions? 19
- HD Wallet vs Descriptor Wallet: What's the Deal? 3
- New Wallet Regulations for Crypto Purchases Over $10K in the US 15
- Creating a Brain Wallet Generator with Bash 15
- Need help migrating my old wallet.dat to the latest version 4