question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] 1.3.0 wallet is not recognizing old coins after a clean sync.

See original GitHub issue

What 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:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:12 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
iliasorazovcommented, Apr 15, 2022

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.

0reactions
emlowecommented, May 11, 2022

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

1.3 is live : r/chia - Reddit
Wallets with large number of transactions or large number of coins will take longer to sync (more than a few minutes), but should...
Read more >
Chia Miner - Blockchain Database Sync Problem - YouTube
If you want to support me - just visit my Amazon Store - big thanks!https://www.amazon.de/shop/brightersantitan》》》Discord:Falls Ihr Bock ...
Read more >
1.3.3 keys to success upgrade now! - General Chia Discussion
When I upgraded from 1.3.0 to 1.3.2 a couple of weeks ago, my wallet was missing some of my coins and a lot...
Read more >
Ledger device firmware update - FAQ
Here you will find all the answers to the most common questions regarding the device firmware update. Does the update affect my crypto......
Read more >
Chia Blockchain 1.3.0
Integrated lite wallet sync - to get you synced up faster while your full node ... to specify how many cores Chia will...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found