feat: revalidate invalid utxo #5020
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stringhandler
previously approved these changes
Dec 8, 2022
Cifko
force-pushed
the
invalid_utxo_revalidation
branch
from
e17e476 to
1758f0f
Compare
Done. |
stringhandler
approved these changes
Dec 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add
last_validation_timestampforInvalid/CancelledInboundtransactions.Configurable interval for revalidation
num_of_seconds_to_revalidate_invalid_utxos. Default is 3 days. When set to zero, the revalidation will be run every time. When revalidation failes, thelast_validation_timestampis updated.How Has This Been Tested?
Partially (revalidation to valid tx).