Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 14/06/2025, 00:22:14 UTC
I have, in fact, either written or reviewed all of the Bitcoin Core wallet code.

Fair enough, and I can confirm I've not encountered this scenario on Bitcoin Core or Litecoin or any of the more popular (and thus better maintained?) crypto wallets.

One specific usecase where keypoolrefill and rescan did not result in an outcome was with a lesser known altcoin named 'Shibacoin'. When I had a wallet break it basically 'lost' all funds that were on change addresses. Repeated keypoolrefills and rescans didn't do much better.

However importing the public keychange address where the funds were sitting (as checked from the explorer) brought results.

I didn't completely understand your point about 'change detection' breaking by using this method. Can you elaborate?
Original archived Re: An approach to recover change addresses from old wallet.dat backups
Scraped on 14/06/2025, 00:17:32 UTC
I have, in fact, either written or reviewed all of the Bitcoin Core wallet code.

Fair enough, and I can confirm I've not encountered this scenario on Bitcoin Core or Litecoin or any of the more popular (and thus better maintained?) crypto wallets.

One specific usecase where keypoolrefill and rescan did not result in an outcome was with a lesser known altcoin named 'Shibacoin'. When I had a wallet break it basically 'lost' all funds that were on change addresses. Repeated keypoolrefills and rescans didn't do much better.

However importing the public key brought results.

I didn't completely understand your point about 'change detection' breaking by using this method. Can you elaborate?