Multi-account support for transaction submission
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend-api-design, blockchain
Research direction
Start by reviewing the custom transaction submission client in dependency issue #4 and the Cosmos SDK auth module's BaseAccount.Sequence reference. Done means supporting configured funded accounts with independent nonce handling, account selection, safety limits, and graceful removal of unhealthy accounts as described in this issue.
Written by the indexing model from the issue text.
Description
Summary
Support submitting blobs from multiple funded accounts to avoid nonce contention when writing to a single namespace at high throughput.
Problem
When a single account submits transactions concurrently, nonce (sequence number) conflicts cause failures:
- Tx A gets nonce 5, Tx B gets nonce 5 → one fails with "account sequence mismatch"
- Serial submission avoids this but kills throughput
- Mempool ordering is not guaranteed, so even sequential nonce assignment can race
Design
Account pool
- Configure multiple funded accounts (key/mnemonic per account)
- Round-robin or least-recently-used assignment when a submission is requested
- Each account manages its own nonce sequence independently
Nonce management
- Track pending nonce per account locally (don't rely solely on on-chain query)
- Increment optimistically on broadcast, roll back on rejection
- Handle sequence mismatch errors by re-querying and retrying from the correct nonce
Configuration
[submission]
enabled = true
[[submission.accounts]]
name = "submitter-1"
key_file = "./keys/submitter-1.json"
[[submission.accounts]]
name = "submitter-2"
key_file = "./keys/submitter-2.json"
[submission.pool]
strategy = "round-robin" # or "least-pending"
max_pending_per_account = 4
Safety
- Monitor account balances, alert when low
- Cap max pending transactions per account to bound risk
- Graceful degradation: if an account is unhealthy (repeated failures, low balance), remove from rotation
Dependencies
- Requires #4 (custom transaction submission client) — nonce management is tightly coupled with how we build and broadcast transactions
References
- Cosmos SDK sequence/nonce model:
authmoduleBaseAccount.Sequence
- Dominant language
- Go
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evstack/apex
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bazel-contrib/rules_go#4721 · 2 comments ·
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
bug carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·
-
area/logging kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100