MEV-Boost Relayers: Selling Blockspace to Builders

Key Takeaways

• MEV-Boost relayers connect validators to a competitive market of block builders using proposer-builder separation.
• The relay holds the block payload in escrow until the validator signs the header, then releases it.
• The main risk is trust and centralization: a few relays handle most blocks and can censor transactions.
• Validators using MEV-Boost can earn meaningfully more than building blocks on their own.

What It Is

MEV-Boost is open-source software a validator runs alongside its node. It implements proposer-builder separation (PBS), splitting two jobs that used to be one. The proposer is the validator chosen to add the next block. The builder is a specialist who assembles the most profitable ordering of transactions.

The relay is the trusted middleman that connects them. Builders submit full blocks to relays, relays pick the most valuable one, and the validator signs a commitment to that block before ever seeing its contents. MEV here means maximum extractable value, the extra profit available from how transactions are ordered.

The Intuition

Ordering transactions profitably is hard and competitive. Left to do it alone, only the most sophisticated validators would capture that value, which would push smaller validators to drop out and centralize the network.

PBS fixes the incentive. It lets any validator, even a hobbyist running one node at home, auction off its block to professional builders and collect the proceeds. The validator stays simple and decentralized while the complex work happens in a separate, competitive market. Spreading that value broadly is the whole reason the design exists.

How It Works

The flow runs through a strict sequence designed to protect both sides:

1. Builders construct full blocks and submit them to relays
2. Relays validate blocks and rank them by value
3. Validator (via MEV-Boost) asks relays for the best header
4. Validator signs the winning header, committing to it
5. Relay releases the full block payload to the validator
6. Validator publishes the block to the network

The relay performs two safety jobs. It checks that each submitted block is valid so the validator does not sign something broken. And it holds the block body in escrow, releasing it only after the validator signs the header. This stops the validator from stealing the builder's transaction ordering, and stops a builder from handing over an invalid block.

A relay typically exposes three interfaces: a proposer API the validator calls, a builder API the builders submit to, and a data API for read-only access. Validators can connect to several relays at once and simply take the highest bid.

Worked Example

Suppose a validator is chosen to propose the next block. Its MEV-Boost software queries three relays. Relay A returns a header worth 0.05 ETH, Relay B returns 0.08 ETH, and Relay C returns 0.06 ETH.

The validator picks Relay B's header because it pays the most. It signs that header, committing to publish exactly that block. Only then does Relay B release the full list of transactions. The validator publishes the block and pockets the 0.08 ETH, far more than the roughly 0.03 ETH it might have earned arranging transactions itself.

Now consider the trust problem. The validator signed before seeing the contents. If Relay B is honest, everything works. But the validator relied on the relay to have validated the block and to release it on time. That reliance is the soft spot that the rest of the design tries to minimize but cannot fully remove.

Common Mistakes

1. Believing PBS removes MEV. It does not. MEV-Boost redistributes the value to validators and organizes the market. The sandwich attacks and arbitrage still happen inside builder blocks; PBS just changes who profits and how the auction runs.

2. Ignoring relay centralization. A small number of relays handle a large share of Ethereum blocks. If a dominant relay censors certain transactions, that censorship propagates widely. Concentration here is a live decentralization concern.

3. Assuming relays are trustless. They are trusted parties. The validator signs a header before seeing the block, so a malicious or buggy relay could in principle misbehave. Running multiple relays reduces but does not eliminate that exposure.

4. Confusing builders with validators. Builders order transactions for profit; validators propose blocks and secure the chain. PBS separates them on purpose. Treating them as the same role misses the point of the design.

5. Overlooking censorship trade-offs. Some relays filter transactions to comply with regulations. Validators choosing only those relays contribute to chain-level censorship, which conflicts with the neutrality goal that PBS was partly meant to protect.

Frequently Asked Questions

What are MEV-Boost relayers in simple terms? MEV-Boost relayers are middlemen that let an Ethereum validator auction off the right to fill its block to professional builders. The relay collects bids, hands the validator the best one, and releases the block only after the validator commits to it.

How does the MEV-Boost proposer-builder market affect investment decisions? For anyone staking, MEV-Boost can raise validator rewards by tapping the builder market. The trade-off is added reliance on a handful of relays, so the extra yield comes with centralization and censorship risk worth weighing.

What is a real-world example of MEV-Boost in action? When a validator is picked to propose a block, its software polls several relays, takes the highest paying header, signs it, and only then receives the actual transactions to publish. The bidding war is what raises the validator's payout.

How can validators use MEV-Boost relayers effectively? Connect to multiple independent relays rather than one, so no single relay can dictate or censor your blocks, and review each relay's transaction-filtering policy to understand the censorship trade-off you are accepting.

How are MEV-Boost relayers different from plain MEV? MEV is the underlying profit from ordering transactions, while MEV-Boost relayers are the infrastructure that auctions that opportunity through proposer-builder separation. Relayers organize and distribute MEV; they do not eliminate it.

Sources

1. Flashbots Docs. "MEV-Boost Overview." https://docs.flashbots.net/flashbots-mev-boost/introduction
2. Flashbots. "MEV-Boost in a Nutshell." https://boost.flashbots.net/
3. Flashbots. "mev-boost-relay." https://github.com/flashbots/mev-boost-relay
4. Flashbots. "mev-boost." https://github.com/flashbots/mev-boost

Disclaimer

This article is educational content only and is not financial advice. Nothing here is a recommendation to buy, sell, or hold any security. Consult a licensed advisor before making investment decisions.