Jump to content
The Coin Wire

Crypto moves, protocols and policy

MEV-Boost Relay Outages and Block Proposals

When a MEV-Boost relay goes offline, its bids disappear from the slot; another relay or local block building can keep the proposal moving before the deadline.

By The Coin Wire Editorial4 min read

MEV-Boost Relay Outages and Block Proposals

When a MEV-Boost relay goes offline, its bids drop out of consideration, while another relay or local block building can still support the proposal. The proposer’s consensus client requests bids through MEV-Boost and can use its execution client to build locally if no acceptable bid arrives in time.

The outage matters only when it leaves the proposer without a usable option before the client’s deadline. The result depends on which relays are configured and reachable, how quickly they respond, and how the validator’s client is set up.

MEV-Boost lets a validator’s consensus client request block bids from configured relays for a slot. Each available relay can return a builder’s bid; MEV-Boost passes an acceptable option back to the client, which uses it in the proposal process. A relay that is offline contributes no bid to that choice.

Flashbots relay coverage makes the topic concrete: a discussion of Flashbots relay trust and coverage explains why reachability and relay selection matter alongside the bid itself. With multiple relays configured, losing one connection can leave other bids available.

One offline relay can leave other bids available

When one relay stops responding, MEV-Boost can still use a usable bid returned by another configured relay in time. A single relay outage therefore does not, by itself, stop a validator from proposing.

Take a validator with two relays configured for its slot. MEV-Boost requests bids from both. One relay is offline and returns nothing; the other responds before the client’s deadline with an acceptable bid. The available bid can still support the proposal, even though one source has disappeared.

The choice is narrower than it would have been with both relays responding: the offline relay’s bid is missing from consideration. That can mean missing a more attractive external bid, but it does not tell us what that relay would have offered. Relay count alone also cannot guarantee coverage. The other relay has to be reachable and return a usable bid within the available time.

Flashbots is one relay name a validator may encounter when considering coverage. The practical question is whether the configured set gives MEV-Boost another timely source when one relay fails, not simply how many names appear in a configuration.

No timely bid can lead to local block building

With no acceptable relay bid before the deadline, the consensus client can fall back to local execution and build a block using the validator’s execution client. That gives the proposer another route to produce a block, though it may miss the external builder’s bid.

Consider a slot where every configured relay is unreachable or returns no acceptable bid before the client needs to act. With local fallback enabled and supported by the client configuration, the proposer can build locally instead of relying on a relay-provided block. The external builder’s opportunity to supply the selected bid has passed for that slot.

This fallback is not automatic in every setup. Client behavior and timing depend on configuration, including whether local execution is available and when the client stops waiting for relay responses. A validator should understand its own client settings before assuming that an outage will lead to local building.

The trade-off is between waiting for an external bid and preserving time for the local path. More relay connections can provide more chances to receive a bid, but each response still has to arrive in time. Local building offers an alternative when no bid is usable; it does not recreate a bid that was never received.

Related

How can I check whether a MEV-Boost relay is reachable?

To check reachability, inspect the validator’s MEV-Boost and client monitoring for connection status and relay responses. A relay that is configured but unreachable cannot contribute a bid to the current slot; response timing also matters, since a late bid may not be usable.

Does a relay outage affect the validator’s next slot?

A relay outage affects a slot only when that relay would have served a proposal for which the validator is responsible. The next slot can have a different proposer and different relay conditions. For a validator’s later slot, the key signals are whether the relay has recovered, whether other configured relays respond, and whether the client configuration still supports its intended fallback.

A relay outage removes one possible bid; it becomes a proposal problem only when no usable alternative arrives before the deadline. For validators, relay coverage, response timing, and local fallback settings determine whether the slot can proceed with another bid or a locally built block.