-
Notifications
You must be signed in to change notification settings - Fork 15
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
After fast sync wallet is not in the same state as after pruning #896
Comments
kostyantyn
changed the title
After the fast sync wallet is not in the same sate as after the pruning
After the fast sync wallet is not in the same state as after the pruning
Apr 4, 2019
Since this is tagged I would prefer not to rush this for a perceived quick win. Especially the wallet (pruning, fast sync, SPV/light, merging with bitcoin 0.17, 0.18) will require some serious thinking. |
scravy
changed the title
After the fast sync wallet is not in the same state as after the pruning
After fast sync wallet is not in the same state as after pruning
Apr 5, 2019
I do. Edited. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
CMerkleTx
has a fieldnIndex
which contains the position of the transaction in the block. We also don't have this field and it's set to 0.Describe the solution you'd like
A node can recover missing inputs by asking peers for its full transactions.
To recover the position, we can either request the full block (too slow) or create a new p2p message that returns the needed leaves to reconstruct the merkle root and the position of our transaction.
The text was updated successfully, but these errors were encountered: