feat: Add Option to Override SequenceNumber and Bypass Network Fetches#2
Merged
DavidNzube101 merged 1 commit intomasterfrom Apr 9, 2026
Merged
feat: Add Option to Override SequenceNumber and Bypass Network Fetches#2DavidNzube101 merged 1 commit intomasterfrom
DavidNzube101 merged 1 commit intomasterfrom
Conversation
Collaborator
|
Awesome |
Collaborator
|
CI passes too :)
|
DavidNzube101
added a commit
that referenced
this pull request
Apr 13, 2026
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
2 participants
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.
Fixes #1
The Problem
Currently, when constructing a transaction, the Kit strictly fetches the account's sequence number from the RPC node via GetAccountInfo. For applications that require high-frequency, concurrent transaction submissions (like Keeper bots or intensive indexers), this strict fetch creates a severe bottleneck. Multiple goroutines fetching at the same time will pull the exact same sequence number, resulting in immediate "Transaction already in mempool" collisions and transaction failures on the node.
The Solution
This PR introduces the ability for clients to opt-out of the automatic network fetch by providing their own sequence number, empowering them to manage sequence state optimistically in memory.