SUAVE primary sources

Reviewed: 2026-05-10 UTC

Core project framing

https://writings.flashbots.net/the-future-of-mev-is-suave
- Foundational Flashbots post introducing SUAVE.
- Used to confirm the main problem framing around exclusive orderflow, cross-domain MEV, and the attempt to unbundle the mempool and block-builder role from existing chains into a shared layer.
https://raw.githubusercontent.com/flashbots/suave-specs/main/README.md
- Canonical protocol-specs repository README.
- Used to confirm the current public framing of SUAVE, the alpha-state warning, the live-spec role of the repo, the Rigil / Toliman / Sirrah tracks, and the Centauri / Andromeda roadmap split.

https://writings.flashbots.net/mevm-suave-centauri-and-beyond
- Best source for the practical architecture described after the initial announcement.
- Used to confirm the MEVM framing, the idea of SUAVE as a market for mechanisms, the role of execution nodes and confidential data stores, the bid model, and the staged trust model from centralized execution nodes toward TEE and cryptographic hardening.

SUAVE’s distinctive mechanism is shared sequencing plus programmable confidential execution, not just “private orderflow” or another builder brand.
The most important control surfaces are execution-node operation, access to confidential data, precompile design, bridge/export paths, and the roadmap from trusted operators toward TEE / cryptographic hardening.
SUAVE is most valuable as a comparison class because it decomposes MEV infrastructure into preference expression, confidential compute, executor competition, and block export rather than flattening all of that into one generic builder label.
The current documentation posture itself is informative: the public docs endpoint has been decommissioned, while the writings and specs repo remain the clearest sources of truth. That is a reminder to treat SUAVE as a living research-and-implementation program rather than a finished stabilized protocol.