Partial fix for nonce ordering under parallel txs#6
Merged
julienh-ssv merged 1 commit intostagefrom Oct 28, 2025
Merged
Conversation
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.
This PR attempts to focus on the 80% results with only 20% code changes. The goal is to fix the issue when parallel transactions fail due to nonce collisions.
Approach:
The reservation should cover 90% of our current use cases (in e.g. frontend) and the expiration is a safety fallback in case client crashes mid-way and never uses the reserved nonce. This prevents blocking future tx that would get a higher nonce reservation.