Skip to main content
Hashbeam

Crypto protocols, markets and policy

fbb448

How to See What an Ethereum MEV-Boost Relay Sees Before Signing

What can an Ethereum MEV-Boost relay see? It sees submitted payload transactions and their order, while the validator signs a blinded header first.

The Hashbeam Desk··4 min read

How to See What an Ethereum MEV-Boost Relay Sees Before Signing

An Ethereum MEV-Boost relay can see the full execution payload a builder submits to it, including transaction contents and order, because it checks and brokers that block before the validator signs a blinded block. The validator sees the header and bid information first, then receives the matching payload from the relay after signing.

That boundary matters when you are judging who can see a transaction and who must be trusted: Flashbots trust by layer changes how to interpret this relay-level view. Flashbots Relay sees the payloads submitted to it, while a private route to another endpoint stays outside that view unless its transaction later enters a block submitted there.

What does the relay see before the validator signs?

The relay sees the builder’s complete candidate block before it sends a blinded block header to the validator. A blinded block contains an execution payload header rather than the full execution payload, so the validator can consider and sign the block without seeing its transactions at that stage.

The sequence for one proposed block is:

  1. Builder submits the payload. The builder sends the complete execution payload to a relay. It includes the transactions and their order.
  2. Relay checks and brokers it. The relay checks the submitted block and offers it to the validator through a blinded block header with bid information.
  3. Validator signs the blinded block. The validator signs the header without first receiving the full payload.
  4. Relay returns the payload. After receiving the signed blinded block, the relay returns the matching execution payload so it can be published.

Take a validator choosing between candidate blocks for a proposal. Before it signs, the relay handling a candidate can inspect that candidate’s transactions and ordering. The validator sees the bid information and the execution payload header, not those transaction details. Once the validator signs, the relay returns the payload associated with that header.

This distinction helps when assessing transaction privacy. A relay’s early view is limited to blocks builders submit to it; using MEV-Boost does not give that relay automatic visibility into every pending transaction sent privately elsewhere. A transaction routed to another endpoint is outside the relay’s view unless it later becomes part of a payload submitted there. The relay’s visibility follows the data it receives, not every route a transaction might take.

What stays outside the relay’s view?

A relay does not see a privately routed transaction merely because it is a relay in the MEV-Boost flow. Its view covers payloads submitted to that relay. The builder constructs the candidate block and sends it; the validator receives a blinded header first; the relay that handles the submission sees the full payload.

For example, say you send a transaction through a private endpoint that does not submit it to a particular relay. That relay cannot inspect the transaction from this path alone. If a builder later includes it in a candidate payload and submits that payload to the relay, the relay can then see the transaction and its position in that block. The change in visibility happens when the payload reaches the relay.

The three roles therefore have different views. The builder assembling a candidate handles its contents and ordering. The relay sees the full payload submitted to it and provides the blinded header and matching payload in the proposal flow. The validator sees bid information and the header before signing, then receives the payload afterward. A blinded block limits what the validator sees before signing; it does not hide the payload from the relay that brokers it.

Related

What happens if a MEV-Boost relay goes offline?

An offline relay interrupts its part of the proposal path. Before signing, the validator cannot receive a bid or blinded header from that relay; after signing, it cannot retrieve the matching payload from an unreachable relay at that moment. The relay’s outage concerns submissions and proposals using that endpoint, rather than transactions routed privately elsewhere.

Can an Ethereum validator connect to multiple relays?

Yes, a validator can use multiple relay endpoints. Each relay sees the payloads submitted to it, so connecting to several does not give every relay a view of every private transaction or every builder’s submissions. For a validator comparing bids, the useful privacy question is which relays receive candidate payloads and which transaction routes eventually feed those candidates.