How MEV relays work on Ethereum: bids, trust and fallback

How MEV relays work on Ethereum: bids, trust and fallback


MEV relays on Ethereum let a validator choose a builder’s paying block before seeing its transactions, then deliver the full block after the validator signs. Flashbots develops MEV-Boost, the open-source software that runs alongside a validator’s consensus client, and operates Flashbots Relay, which checks bids and holds builder payloads until they are signed. Builders need the relay to keep their blocks private until commitment; proposers rely on it to check bids and deliver the promised block.

  • Trace the handoff from builder submission to signed Beacon Chain block.
  • Identify when relay trust can turn a winning bid into a missed slot.

How does a relay turn a builder’s bid into a proposed block?

An MEV relay receives full blocks and bids from builders, simulates the blocks, and checks that each valid block pays the proposer’s fee recipient at least the amount bid. Before the slot, validators register that fee recipient and their preferred gas limit with relays. The relay uses those details when checking submissions, then offers its best eligible bid through the builder API as a blinded header: a commitment to the block without its transactions.

When the proposer’s turn arrives, MEV-Boost sends a getHeader request to every configured relay and selects the highest eligible bid returned. The proposer signs a blinded Beacon Chain block containing that header. MEV-Boost sends the signed block back to the relay that supplied it; the relay reveals the matching payload so the complete block can be broadcast. This commit-reveal sequence keeps the builder’s contents hidden until the proposer commits to them.

Say a validator connects to Flashbots Relay, a bloXroute relay, and a third relay. Titan Builder submits a block that produces the top bid at one of them. MEV-Boost returns that relay’s header to the proposer, and the builder’s payment lands at the validator’s registered fee recipient when the complete block is included. The validator compares bids without having to simulate three builders’ blocks.

The timing of the signature defines the failure case. Before signing a relay header, the proposer can use a locally built block if bids are absent or the relays fail to respond. After signing, a fallback block for the same slot would be a conflicting proposal, or equivocation, and could be slashed. If the selected relay then withholds the payload or fails to deliver it in time, the proposer cannot safely switch blocks and misses the slot.

For routine operation, the MEV-Boost -min-bid setting rejects bids below a chosen threshold and lets the consensus client use its local block. A higher threshold can pass up builder payments, but it reduces how often the validator depends on a relay to finish a proposal.

What is the difference between a block builder and a relay?

A block builder assembles transactions and bids for the right to supply a block. A relay checks builders’ submissions, holds their payloads, and brokers bids to proposers. MEV-Boost compares offers across the relays a validator has chosen.

Can a relay see or steal a builder’s MEV?

A relay sees the full block it checks, including its transaction ordering, so builders trust it with valuable information. A dishonest relay could leak that information or use it to compete with the builder. Builders therefore assess a relay’s handling of payloads, while validators assess its validation and delivery record.

Choose relays and a minimum bid with the signed-header boundary in mind: once you sign, that relay must deliver the block for the slot to succeed.

Report Page