This repository hosts the current SUAVE protocol specifications. For SUAPP developers please check out our developer docs.
Discussions about design rationale and proposed changes can be brought up and discussed on the Flashbots forum. Solidified, agreed-upon changes to the spec can be made through pull requests.
SUAVE - Single Unifying Auction for Value Expression - is a platform for building MEV applications such as OFAs and block builders in a decentralized and private way.
Read more about SUAVE:
- https://writings.flashbots.net/the-future-of-mev-is-suave
- https://writings.flashbots.net/mevm-suave-centauri-and-beyond
See also: suave-geth, suapp-examples
Specifications for the SUAVE protocol are split into two main tracks, Centauri and Andromeda.
| Testnet | Phase | ChainID | Specs |
|---|---|---|---|
| Rigil | Big Bang | 16813125 |
• SUAVE chain • MEVM • Precompiles • Confidential Data Store • Bridge • Kettle |
| Toliman | Big Bang | 33626250 |
• SUAVE chain • MEVM • Precompiles • Confidential Data Store • Bridge • Kettle |
| Sirrah | Proto-Collision |
Centauri is focused on exploration and developer experience, serving as a spec for the secure instantiation. The plan is a progression of three testnets in the direction of increasing functionality and scalability.
Andromeda is the secure instantiation using SGX and cryptography, focusing on privacy with trust minimization. The plan is a progression of three milestones in the direction of better hardening and trust minimization.
Proto-Collisions are plans to sync up between these two development tracks. They represents points where parts of Centauri testnets can be run in secure and trust minimized fashion. Permissioned components from Proto-Collisions, if self-contained, could be used with Ethereum mainnet.
Collision is where the entirety of the SUAVE protocol can be safely deployed for use with Ethereum mainnet in a trust minimized and permissionless fashion.
You are welcome to open PRs and issues. We invite you to discuss your ideas in the Flashbots Forum for greater visibility and to avoid doing work that is unlikely to be widely accepted and merged into the core specs.
For creating tables of contents, we use the "Markdown All in One" VS code extension. This extension comes with a lot of keyboard shortcuts, which may override the ones you are already using. You can disable keyboard shortcuts for this extension by going to "Settings -> Keyboard Shortcuts" (cmd+K cmd+S) and searching for markdown.ext (see #22 for more details).
However, we don't need the ToCs and some other content (like this paragraph) rendered in the documentation frontend. Therefore, please add the <div className="hide-in-docs"></div> to any content that should not appear in the FE.
Made with ☀️ by the ⚡🤖 collective.