MEV-Boost

  • Name: MEV-Boost
  • URL: https://docs.flashbots.net/flashbots-mev-boost/introduction
  • Category: proposer-builder-separation middleware / validator-side block-auction sidecar / relay-aggregating execution market interface
  • Tags: ethereum-ecosystem
  • Summary: MEV-Boost is best understood not merely as validator software, but as the transitional market structure that operationalized proposer-builder separation on post-Merge Ethereum before enshrined PBS. Its core mechanism is simple and powerful: a validator outsources block construction to a competitive builder market through a local sidecar that queries multiple relays and returns the highest-paying valid bid. The analytically important consequence is that MEV-Boost does not just improve validator revenue; it inserts relays as high-trust routing and escrow chokepoints between builders and proposers, making it a key comparison class for builder specs, relay governance, censorship debates, and later enshrined-PBS design.
  • What it does:
    • Runs as middleware next to an Ethereum consensus client so validators can outsource block construction to external builders
    • Connects validators to one or more relays, each of which aggregates bids from one or more builders and returns the most profitable valid header
    • Implements the proposer-side flow for registerValidator, getHeader, and submitBlindedBlock under the builder API / blinded-block pipeline
    • Lets validators configure relay sets, minimum acceptable bid thresholds, request timeouts, and optional timing-game behavior
    • Provides a practical out-of-protocol PBS market that became standard infrastructure for Ethereum block production before enshrined PBS exists in-protocol
  • Key claims:
    • Flashbots’ docs and repo both define MEV-Boost as open-source middleware run by validators to access a competitive block-building market, explicitly framing it as an initial implementation of proposer-builder separation for proof-of-stake Ethereum.
    • The most important mechanism is not just “outsourced block building”; it is a two-layer auction interface. Builders compete inside relays, and relays then compete inside the validator’s local MEV-Boost instance. That structure matters because practical market power can concentrate at either layer.
    • The relay layer is the core trust shift. Flashbots’ relay docs describe relays as doubly trusted by builders for fair payload routing and by proposers for validity, accuracy, and data availability. That makes relay selection a governance and censorship surface, not a neutral infrastructure choice.
    • MEV-Boost is especially useful in the corpus because it turns the abstract PBS idea into an operational dependency graph: validator client MEV-Boost sidecar relay set builder market. Each hop creates a different failure mode, policy surface, and centralization risk.
    • The circuit-breaker guidance in the relay docs is part of the mechanism, not an implementation footnote. Client teams need explicit fallback logic for when the external builder network should be ignored and local block production resumed, which shows how MEV-Boost changes liveness and safety assumptions.
    • The CLI and API surface also reveal economic control knobs. -min-bid, multi-relay routing, request timeout tuning, and advanced timing-game behavior let operators decide how aggressively to chase auction value versus local safety or simplicity.
    • In historical terms, MEV-Boost belongs in the corpus as the real bridge between Ethereum’s pre-PBS proposer role and the later enshrined-PBS design conversation. It is the canonical deployed example of how block-building specialization reconfigures validator power without fully removing trusted intermediaries.
  • Whitepaper: No canonical standalone MEV-Boost whitepaper surfaced in this pass. The strongest primary materials were the Flashbots MEV-Boost docs, the stable-branch repository README, the relay fundamentals page, and the builder spec reference collected in ../whitepapers/mev-boost-primary-sources-2026-05-10.md.
  • Sources:

Internal linkages

  • Keep this note on the strongest nearby reads: flashbots-auction, buildernet, and commit-boost.

  • Useful cut: MEV-Boost is the deployed validator-side PBS sidecar; sequencing-rights and preconfirmation notes can point upward here when the shared issue is proposer-edge policy.

  • Last reviewed: 2026-05-27 UTC