BM-2022: retry lock transactions under same nonce with bumped fees - #1346
Closed
austinabell wants to merge 3 commits into
Closed
BM-2022: retry lock transactions under same nonce with bumped fees#1346austinabell wants to merge 3 commits into
austinabell wants to merge 3 commits into
Conversation
austinabell
changed the title
austinabell
force-pushed
the
austin/retry_same_nonce
branch
from
December 2, 2025 17:26
7ce8868 to
28a02d7
Compare
github-actions
Bot
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Draft until decided whether or not to re-use this nonce for other lock transactions. Would increase complexity to handle cases where the previous tx is locked, but perhaps prevents more locks than the config capacity