-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
simplewallet --restore-deterministic-wallet isn't detecting past transactions #950
Labels
Comments
What git rev did you build from? |
Meaning, it must have become broken before July 8th. |
mmortal03, this patch fixes these issues for me (I was able to reproduce the behavior you experienced). |
Thanks @luigi1111 , I've just finished testing @hyc 's "better fix", and it does seem to fix the problem: 709c724 |
The fix was merged soon after the above was tested, so I'm closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Restoring from deterministic seed isn't detecting any past transactions. MoneroMooo's theory from the bitcointalk thread is that this may be happening because "simplewallet now skips refresh till the block the wallet was created, so there must be a bug that makes it think it doesn't need to refresh those early blocks."
Steps to reproduce:
Run simplewallet --restore-deterministic-wallet
pick a wallet file name
pick a password
Enter an Electrum seed that represents an address with past transactions (you can use the one below)
Let simplewallet scan for past transactions.
Bug: After scanning, no transaction history will be found, and the balance will display as zero, even if the wallet actually has a current balance. Running refresh, rescan_bc, etc. don't help.
You can use the following seed to reproduce the issue:
toilet zeal lion cafe circle ruthless inkling were dauntless jogger custom lagoon suddenly bays torch pager uttered react nurse cause aphid vulture bounced civilian lagoon
This had past transactions that began at block 1088432.
The text was updated successfully, but these errors were encountered: