fix(core-transaction-pool): always apply to sender wallet on acceptChainedBlock #3594
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when a node syncs from genesis, not all transactions are applied to the relevant sender wallets in the transaction pool's
acceptChainedBlock
.This causes issues where the pool wallet state becomes inconsistent with the database wallet state.
By guaranteeing that the sender wallet is always set, the transactions are always properly applied to the relevant wallets on
acceptChainedBlock
, and the state & db wallets remain in sync.