You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
After the fast sync, wallet transactions don't have inputs (as they are not part of UTXO) and wallet doesn't know about all spent transactions. Because of this, we can't see the full log of wallet transactions.
CMerkleTx has a field nIndex 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:
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 1.0, I wonder if #885 is that urgent.
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#883 seems not related much to this. Do you mean #885 ?
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
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: