Optional revalidation of hash/txid for unspent balances #8
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.
ASSERT_UNSPENT_TRANSACTION_HASH_CONFIRMATION_IS_VALID
In certain cases, the sweep function encounters addresses with incomplete or unconfirmed 'unspent' balances. To address this, I have introduced the
getTransactionConfirmationStatus
function, which depends on theASSERT_UNSPENT_TRANSACTION_HASH_CONFIRMATION_IS_VALID
environment variable. By default,ASSERT_UNSPENT_TRANSACTION_HASH_CONFIRMATION_IS_VALID
is set tofalse
.If you have experienced errors such as:
Error validating transaction: Transaction - {{ txHash }} orphaned, missing reference {{ txHash }}
, this patch will be beneficial. It ensures that transaction hashes are validated for confirmation status, reducing the likelihood of encountering orphaned or missing reference errors.