Multi-account support for transaction submission

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

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

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: auth module BaseAccount.Sequence
Dominant language
Go
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evstack/apex

All issues in evstack/apex

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.