How MEV-Boost delivers a signed block to Ethereum
How MEV-Boost delivers a block to an Ethereum validator: the proposer signs a blinded bid, then MEV-Boost fetches its payload for publication.
By The Coin Wire Editorial4 min read

MEV-Boost delivers a builder’s block to an Ethereum validator by gathering relay bids during the proposer duty, then retrieving the chosen payload after the proposer signs its blinded block; without a usable bid, the validator can propose locally.
Take a validator whose consensus client signals that it has the proposer duty for a slot. MEV-Boost requests bids from the relays configured for that validator, giving the proposer a choice of blocks assembled by builders. The available bids depend on which relays MEV-Boost contacts. Flashbots relay coverage is one factor in that view; Flashbots relay bids and coverage explains how relay selection affects what validators can receive.
How does MEV-Boost deliver the selected block?
MEV-Boost presents bids from configured relays so the proposer can choose a block for its slot. A builder assembles transactions into a candidate block and submits it, with a bid, through a relay. The relay checks and forwards the bid and its blinded header to MEV-Boost.
The header gives the proposer information about the offered block and its bid value without exposing the full execution payload. The payload contains the block’s execution contents, including the transactions the builder arranged. The relay returns the header and value so the proposer can consider the offer before those contents are revealed.
Suppose two builders offer blocks for the same slot. One offers a higher bid than the other, and the proposer chooses it based on that value. MEV-Boost does not make that choice for the proposer: it presents the available bids. The deciding factor in this example is the bid value; the builders still constructed the candidate blocks, and the proposer still selected the bid.
After choosing, the proposer signs a blinded beacon block that commits to the selected header. That signature is the commitment to the choice. MEV-Boost then asks the relay for the execution payload matching that header. The relay returns the payload, and MEV-Boost passes it to the consensus client, which combines it with the signed block and publishes the complete block to the Beacon Chain.
The sequence separates the decision from revealing the full transaction contents: the proposer signs the blinded block first, and MEV-Boost retrieves the matching payload afterward. The result is a signed, complete beacon block for the slot. A relay is part of the route that checks and forwards bids and payloads; the builder constructs the block, while the proposer selects and signs the offer.
What changes when a builder supplies the block?
With MEV-Boost, the proposer can consider blocks built externally without handling their full transaction contents before selecting a bid. In a locally built block, the proposer’s own block-building route supplies the candidate. With a builder bid, an external builder assembles the candidate and submits it through a relay. Both routes lead to a block proposed for the slot, but they place block construction in different hands.
That separation comes with a dependency: the selected relay must return the payload that matches the signed header. MEV-Boost connects the validator’s consensus client to relays for bids and payloads, but it does not reorder transactions itself. The builder determines the proposed transaction arrangement; the relay checks and forwards what the builder submitted. Flashbots is one organization associated with this relay infrastructure, and its role in the path is the relay connection rather than the proposer’s block selection.
If no usable bid arrives, the validator can use a locally built block instead. The fallback changes the source of the candidate block, not the publication goal: the consensus client still publishes a complete signed block for the slot. The relevant signals during a proposer duty are whether configured relays return usable bids and whether the chosen relay supplies the matching payload after the blinded block is signed.
Related
What is a blinded block in MEV-Boost?
A blinded block is the proposer’s signed block commitment with the execution payload withheld until after signing. Its header identifies the selected offer, allowing MEV-Boost to request the corresponding payload from the relay.
What happens if MEV-Boost has no bid?
If MEV-Boost has no usable bid for the proposer duty, the validator can fall back to a locally built block. That gives the consensus client a block to complete and publish for the slot.
For a particular proposer duty, check which relays MEV-Boost is configured to contact and whether they return usable bids. That tells you what choices the proposer can consider before signing.