docs(evm): add parallel nonce submission tutorial for HFT traders - #75
Draft
alexander-sei wants to merge 2 commits into
Draft
docs(evm): add parallel nonce submission tutorial for HFT traders#75alexander-sei wants to merge 2 commits into
alexander-sei wants to merge 2 commits into
Conversation
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>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 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>
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.
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:bad noncerejection under Giga), linked to the existing finality and technical-reference pages.<Steps>from clone and verify throughstatus → 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.buildOpsnippet, 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 (currentColorink,--sei-maroon-50accent). 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-linksandmint validate(strict) both pass. The Mintlify CLI refuses Node 26, so run them vianpx -p node@22 -c 'mint validate'or on Node 22 per.nvmrc.llms.txtis left to the scheduled regeneration workflow; consider triggeringregenerate-llms.ymlafter merge.