Extend get_account_next_index logic#273
Merged
ibraheem-abe merged 4 commits intostagingfrom Feb 24, 2026
Merged
Conversation
camfairchild
approved these changes
Feb 24, 2026
ibraheem-abe
approved these changes
Feb 24, 2026
Merged
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.
get_account_next_index(viaaccount_nextIndex) is mempool-aware, unlikeget_account_nonce.This PR adds
use_cache: bool = Trueto asyncget_account_next_index, allowing callers to fetch a fresh nonce directly from the node and bypass the process-local_noncescache if it passed withFalse.This is needed for flows with an external nonce allocator (like relay endpoint + memcached), to avoid desync between memcached and local
_nonces, which can causefuture/stale nonceerrors and 500s on/api/relay/submit.Note:
Tests fail not bc of PR