mev-boost-primary-sources-2026-05-10

MEV-Boost primary sources

Collected: 2026-05-10 UTC

Primary sources reviewed

• https://docs.flashbots.net/flashbots-mev-boost/introduction
  • Official Flashbots overview page for MEV-Boost
  • Key points used: defines MEV-Boost as open-source validator middleware; frames it as an implementation of proposer-builder separation for PoS Ethereum; describes builders, relays, and validator-side integration
• https://docs.flashbots.net/flashbots-mev-boost/relay
  • Official relay fundamentals page
  • Key points used: relays are doubly trusted intermediaries; relays aggregate builder bids, validate payloads, provide data availability / escrow functions, and expose proposer / builder / data APIs; circuit-breakers and relay monitoring are first-class operational concerns
• https://github.com/flashbots/mev-boost
  • Canonical repository page for the software and surrounding docs/wiki/spec references
  • Used to confirm role, installation surface, API/spec references, and ongoing maintenance posture
• https://raw.githubusercontent.com/flashbots/mev-boost/stable/README.md
  • Best machine-readable primary source reviewed in this pass
  • Used to confirm exact software role, relay / builder flow, CLI control surface (-relay, -relays, -min-bid, request timeouts, metrics), and proposer-side sequence for registerValidator, getHeader, and submitBlindedBlock
• https://ethereum.github.io/builder-specs/
  • Canonical builder API specification referenced directly by Flashbots docs and repo
  • Used as the standard interface context for how MEV-Boost fits into blinded-block PBS flows
• https://ethresear.ch/t/proposer-block-builder-separation-friendly-fee-market-designs/9725
  • Historical Ethereum Research thread linked by Flashbots as the PBS design antecedent
  • Used mainly as provenance for the conceptual lineage rather than for implementation details

Notes

• MEV-Boost is analytically strongest when treated as deployed PBS market structure, not just as validator software.
• The real control surface is the relay layer: builders need fair routing; validators need validity and data availability; both sides inherit trust in relay behavior.
• Multi-relay routing partially decentralizes block sourcing, but also turns relay choice, status checking, and circuit-breaker logic into governance and safety decisions for operators and client teams.
• This entry belongs in the corpus because it makes the path from abstract PBS theory to concrete builder / relay / validator dependency visible.