[Bug] 1.3.0 wallet is not recognizing old coins after a clean sync.
See original GitHub issueWhat happened?
What i did
Upgraded to 1.3
Deleted old wallet db (because it was corrupted for some reason)
wait until wallet synced
What happened
Balance is 0.0
My researches
I checked the default puzzle hash generated by the old-version wallet, and found it still have unspent coin. So the balance shouldn’t be 0.
I checked the derivation_paths
table in the new wallet db on another computer.
Figured out the old-version default puzzle hash has derivation_index = 0, hardened = 0
, while the new-version default puzzle hash has derivation_index = 0, hardened = 1
.
And I thought the new wallet does not recognize the old addresses.
updates
Now the old default puzzle hash received a new coin, the wallet now recognized the new coin, but not the older coins.
So the bug is no longer “new wallet does not recognize old addresses”, and it’s not because the old addresses were generated using non-hardened pubkeys.
Version
1.3.0
What platform are you using?
Linux
What ui mode are you using?
CLI
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:12 (5 by maintainers)
Top GitHub Comments
Apparently the unspent transaction was indeed spent. The problem is probably caused by the fact that my
derivation_paths
list had discontinuity and I didn’t use addresses in a middle of it, so it wasn’t completely filled during conversion and resync. I’ve tried to add the missed puzzlehash row to the db. How to initiate resync against the new list manually? Since the issue is probably different from the posted above I should probably open a new issue.Please test with 1.3.5 as various fixes for this are in 1.3.5. Closing issue. Feel free to re-open if problems continue with 1.3.5