fix: added transaction revalidation to the wallet startup sequence #5227 #5246
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.
Description
Now wallet revalidates all transactions included in the wallet on startup.
#5227
Motivation and Context
Outputs fetched from a fully synced node could be invalidated by the transaction validator, e.g. wallet has normal outputs,
fully validated, but at some point become invalidated when the wallet is trying to negotiate with another, not yet fully synced node that doesn't recognise said output due to not reaching its height at the moment.
So, the code was already there but not yet used in the startup process.
How Has This Been Tested?
manually