flashbots-primary-sources-2026-04-27

Flashbots primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

• Official site: https://www.flashbots.net/
• Docs root: https://docs.flashbots.net/
• MEV-Boost docs: https://docs.flashbots.net/flashbots-mev-boost/introduction
• Protect docs: https://docs.flashbots.net/flashbots-protect/overview
• BuilderNet docs: https://buildernet.org/
• Public GitHub org: https://github.com/flashbots
• Major writings referenced in this pass: https://writings.flashbots.net/the-future-of-mev-is-suave

What the official materials say

1) Homepage / mission surface

• URL: https://www.flashbots.net/
• Key takeaways:
  • Flashbots describes itself as a research and development organization formed to mitigate the negative externalities posed by maximal extractable value (MEV), starting with Ethereum
  • The official mission is framed around three verbs: Illuminate, Democratize, and Distribute
  • The homepage no longer points to just one relay or one research artifact; it maps a broad product-and-research stack including MEV-Boost, BuilderNet, Rollup-Boost, Protect RPC, MEV-Share, and open research
  • This makes Flashbots look like transaction-supply-chain infrastructure and market-structure middleware, not merely an MEV think tank

2) Docs root / ecosystem segmentation

• URL: https://docs.flashbots.net/
• Key takeaways:
  • The docs homepage explicitly segments users into three groups: searchers, Ethereum users, and validators/builders/relayers
  • For end users, the docs foreground Protect RPC and the Scam Victims Hotline; for infrastructure operators, they foreground MEV-Boost
  • The docs also reiterate the Illuminate / Democratize / Distribute framing and point readers to the forum and public GitHub repos
  • This segmentation is a strong categorization clue because it shows Flashbots is operating across user protection, validator middleware, and research coordination simultaneously

3) MEV-Boost

• URL: https://docs.flashbots.net/flashbots-mev-boost/introduction
• Key takeaways:
  • The docs describe mev-boost as open-source middleware run by validators to access a competitive block-building market
  • Flashbots presents MEV-Boost as an implementation of proposer-builder separation for proof-of-stake Ethereum
  • The docs say the goal is greater competition, decentralization, and censorship-resistance, with validators querying multiple relays for profitable blocks
  • This is one of the clearest signals that Flashbots should be cataloged as core Ethereum execution infrastructure rather than only as a research brand

4) Flashbots Protect

• URL: https://docs.flashbots.net/flashbots-protect/overview
• Key takeaways:
  • Flashbots Protect is described as a cheaper and safer way to transact on Ethereum
  • The docs say transactions are sent to a private Flashbots mempool to protect against frontrunning and sandwich attacks
  • The docs also highlight MEV refunds, gas-fee refunds, and the claim that transactions are only included if they do not revert
  • This matters because it shows Flashbots is not only building validator-side or searcher-side infrastructure; it also operates a user-facing transaction-protection product

5) BuilderNet

• URL: https://buildernet.org/
• Key takeaways:
  • BuilderNet is presented as a decentralized block-building network for Ethereum that runs on TEEs and shares MEV with the community
  • The public docs surface emphasizes architecture, API references, and secure orderflow submission
  • This suggests Flashbots’ current roadmap extends beyond MEV-Boost’s market access layer into newer block-building network design and revenue-sharing mechanisms

6) GitHub organization

• URL: https://github.com/flashbots
• Key takeaways:
  • The public organization describes Flashbots as an R&D organization working on the negative externalities of MEV and avoiding existential risks to stateful blockchains like Ethereum
  • The org page explicitly separates efforts into Product, Research, and Coordination
  • The listed surfaces span MEV-Boost, BuilderNet, Rollup-Boost, Protect RPC, SUAVE, and the mev-research collaborative process
  • The GitHub description also highlights grants and Flashbots Research Proposals, reinforcing that open coordination is part of the project’s operating model

7) SUAVE essay / roadmap signal

• URL: https://writings.flashbots.net/the-future-of-mev-is-suave
• Key takeaways:
  • The SUAVE essay frames Flashbots’ next challenge as decentralizing block building itself after isolating MEV’s centralizing effects to builders
  • The post is useful not as a canonical whitepaper, but as a roadmap-level primary source for how Flashbots thinks about cross-domain MEV, sequencing, and decentralization commitments
  • It helps explain why the project’s product surface now spans builder markets, user protection, and experimental execution-market design rather than stopping at MEV-Boost

Whitepaper / technical-doc status

• No single canonical Flashbots company whitepaper or litepaper surfaced in this pass.
• The mission essay, MEV-Boost docs, Protect docs, BuilderNet docs, and GitHub/writings corpus are the most useful current primary sources.
• In practice, the real source of truth is distributed across operational docs and open-source repos rather than concentrated in one PDF.

Research notes

• Best current category for the library: MEV research and execution infrastructure / block-production supply-chain middleware / transaction protection / builder-market infrastructure.
• The key insight is that Flashbots should be cataloged as a multi-layer execution-stack and market-structure project, not just as “the MEV-Boost team” or “an MEV research group.”
• The docs’ explicit split across searchers, users, and validators/builders/relayers is unusually high-signal for understanding the real operating surface.