Repository navigation
Conversation
…nonce gaps getNextNonce() only ever moves forward (max of the L1 node's pending nonce and the locally cached pnonce+1), so it can never rediscover or refill an earlier nonce the service has lost track of locally. Add TX_SUBMITTER_FORCE_NEXT_COMMIT_NONCE (default 0/disabled) to force the next commit tx onto a specific nonce once, then auto-clear so normal nonce selection resumes afterward.
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 48 minutes. View limit details
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
…nonce gaps
getNextNonce() only ever moves forward (max of the L1 node's pending nonce and the locally cached pnonce+1), so it can never rediscover or refill an earlier nonce the service has lost track of locally. Add TX_SUBMITTER_FORCE_NEXT_COMMIT_NONCE (default 0/disabled) to force the next commit tx onto a specific nonce once, then auto-clear so normal nonce selection resumes afterward.