Skip to content

docs(evm): add parallel nonce submission tutorial for HFT traders - #75

Draft
alexander-sei wants to merge 2 commits into
mainfrom
docs/hft-parallel-nonce-submission
Draft

docs(evm): add parallel nonce submission tutorial for HFT traders#75
alexander-sei wants to merge 2 commits into
mainfrom
docs/hft-parallel-nonce-submission

Conversation

@alexander-sei

Copy link
Copy Markdown
Collaborator

What is the purpose of the change?

Add new content: a tutorial and explainer for sei-protocol/sei-parallel-nonce-hft, aimed at high-frequency trading teams building on Sei EVM.

Describe the changes to the documentation

Target audience: HFT and market-making teams who need to submit many independent operations from one funded address and currently work around Sei's sequential nonce model with fleets of hot wallets.

New page evm/hft/parallel-nonce-submission.mdx, in a new High-Frequency Trading group in the EVM tab:

  • Why one account is one queue – sequential nonces, revert vs. never-landed, and the two Sei-specific facts that make this sharper (no pending state; bad nonce rejection under Giga), linked to the existing finality and technical-reference pages.
  • How it works – one subsection per mechanism, each with its own diagram: ERC-4337 two-dimensional nonce lanes, EIP-7702 delegation, gas-only relayers with a private mempool, the bundle lifecycle (write-ahead journal, same-nonce replacement), and failure isolation.
  • The moat – comparison table (single wallet / wallet fleet / public ERC-4337 bundler / nonce lanes) and the structural reasons the design is hard to match, plus the caveat that submission parallelism is not execution parallelism.
  • Tutorial<Steps> from clone and verify through status → delegate → fund → spray, with <Tabs> for a local Anvil Prague fork vs. Atlantic-2, an annotated example report, and the optional real-swap and baseline runs.
  • Tuning, a condensed configuration reference, venue-integration guidance with a buildOp snippet, the production-readiness list from the repo, troubleshooting, and resources.

Supporting changes:

  • snippets/parallel-nonce-diagrams.jsx – six theme-aware SVG diagrams following the existing Giga diagram convention (currentColor ink, --sei-maroon-50 accent). Rendered and checked in both light and dark mode.
  • docs.json – new navigation group.
  • evm/index.mdx – card in Use Cases linking to the page.

Notes

  • mint broken-links and mint validate (strict) both pass. The Mintlify CLI refuses Node 26, so run them via npx -p node@22 -c 'mint validate' or on Node 22 per .nvmrc.
  • No redirects needed (new page, nothing moved). llms.txt is left to the scheduled regeneration workflow; consider triggering regenerate-llms.yml after merge.
  • Throughput figures in the Tuning section are quoted from the repository README as dated measurements (Atlantic-2, September 3, 2026), not protocol limits.

Add a High-Frequency Trading group to the EVM tab with a guide to
sei-protocol/sei-parallel-nonce-hft: how EIP-7702 delegation, ERC-4337
nonce lanes, a private mempool, and gas-only relayers let one funded
address submit many independent operations without a sequential nonce
queue.

- Explain the problem (sequential nonces, no pending state on Sei, strict
  nonce admission under Giga) and each mechanism with its own diagram
- Add a "moat" section comparing the design with single wallets, wallet
  fleets, and public ERC-4337 bundlers
- Step-by-step tutorial for a local Prague fork and Atlantic-2, an
  annotated example report, tuning notes, a configuration reference,
  venue-integration guidance, and troubleshooting
- Six theme-aware SVG diagrams in snippets/parallel-nonce-diagrams.jsx,
  following the existing Giga diagram convention
- Link the page from the EVM home page Use Cases

Co-authored-by: Cursor <cursoragent@cursor.com>
@mintlify

mintlify Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
sei-docs 🟢 Ready View Preview Sep 10, 2026, 12:50 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

…check

The spelling check treats the "Pn"/"pn" prefix as a misspelling of
"on". Rename the snippet components to a ParallelNonce* prefix, matching
the Giga* diagram convention, and give SVG marker ids descriptive names.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant