An MEV-Relay is a critical piece of infrastructure in Ethereum's post-merge proof-of-stake ecosystem. Its primary function is to receive blocks from specialized block builders and forward them to validators (or proposers) for inclusion in the chain. By separating the roles of block building and block proposing, the relay creates a competitive marketplace for block space. This design prevents validators from viewing the contents of a block before committing to it, which mitigates the risk of them stealing the profitable MEV opportunities contained within—a practice known as MEV theft or time-bandit attacks.
MEV-Relay
What is MEV-Relay?
An MEV-Relay is a specialized network node that acts as a trusted intermediary between block builders and validators in a proof-of-stake blockchain ecosystem, designed to mitigate the negative externalities of Maximal Extractable Value (MEV).
The relay operates by receiving encrypted block headers and associated bids from builders. A validator connects to one or more relays to receive these blinded header-bid bundles. The validator then selects the most profitable bid, signs a commitment to propose the associated block, and receives the full, unencrypted block contents from the relay only after this commitment is made. This process, central to proposer-builder separation (PBS), ensures the validator cannot renege on their choice after seeing the profitable transactions. Major relays on Ethereum include the Flashbots Relay, BloXroute, and Eden Network.
Beyond preventing MEV theft, relays enforce critical censorship resistance and credible neutrality rules. For instance, they validate that blocks comply with OFAC sanctions lists or, in the case of censorship-resistant relays, explicitly ensure they do not. They also verify that blocks are valid according to network consensus rules before forwarding them. This gatekeeper role makes relays a focal point for network health and decentralization debates, as reliance on a few dominant relays presents potential centralization risks. The evolution towards native PBS within the Ethereum protocol aims to eventually reduce this reliance on trusted external relays.
Key Features
An MEV-Relay is a specialized network node that acts as a trusted intermediary between block builders and validators in a proof-of-stake blockchain, designed to mitigate the risks of Maximal Extractable Value (MEV).
Trusted Builder-Validator Bridge
An MEV-Relay sits between searchers/block builders and validators/proposers. It receives block proposals from builders, verifies their validity, and presents a curated list to the next validator, who selects the most profitable or desirable block. This creates a permissioned, reputation-based communication layer separate from the public peer-to-peer network.
MEV Mitigation & Censorship Resistance
A primary function is to prevent malicious MEV extraction that harms users. Relays can enforce rules, such as filtering out blocks containing sandwich attacks or time-bandit attacks. However, they also introduce a potential centralization point, as relay operators can censor transactions by excluding certain blocks, making relay diversity critical for network health.
Proposer-Builder Separation (PBS) Enabler
MEV-Relays are the operational backbone of Proposer-Builder Separation (PBS), a design paradigm formalized in Ethereum's roadmap. PBS decouples the role of block proposal (validators) from block construction (builders). The relay facilitates this market by allowing builders to compete on block quality without exposing their full contents to validators prematurely.
Block Auction Marketplace
Relays operate a competitive auction for block space. Builders submit execution payloads (the proposed block's contents) along with a bid (the payment to the validator). The relay ranks these payloads, typically by bid value, and presents them to the validator. This creates a transparent market for MEV, directing profits to validators and builders rather than just the proposing validator.
Payload Privacy & Integrity
To prevent MEV theft—where a validator steals a builder's profitable transaction ordering—relays provide a private communication channel. Builders send their full block payloads only to the relay, which holds them in escrow. The validator only sees block headers and bids until they commit to a specific payload, ensuring the builder's work is not copied without compensation.
Real-World Relay Examples
On Ethereum, major relays include:
- Flashbots Relay: The original relay, promoting transparent and ethical MEV.
- BloXroute: Offers both regulated and permissionless relay services.
- Ultra Sound Relay: Focused on decentralization and minimal trust.
- Agnostic Relay: Aims to be client-agnostic and open. Validator clients like Lighthouse and Teku connect to multiple relays to access different builder markets and ensure censorship resistance.
How an MEV-Relay Works
An MEV-relay is a critical infrastructure component that acts as a trusted intermediary between block builders and validators in a proof-of-stake blockchain network, designed to facilitate the secure and efficient extraction of Miner Extractable Value (MEV).
An MEV-relay operates as a two-sided marketplace and communication protocol. On one side, it receives block proposals from specialized searchers and builders who construct optimized blocks containing profitable transaction bundles. On the other side, it presents these pre-built blocks to validators (or proposers) for inclusion in the chain. The relay's primary function is to receive these candidate blocks, perform basic validity checks, and present them to the validator in a standardized format, often through an API. This decouples the block construction process from the block proposal duty, enabling specialization and competition among builders.
The relay ensures commitment and privacy through a two-phase process. First, builders submit a block header and a commitment to the full block body. The validator selects the most profitable header based on the attached bid. Second, upon selection, the relay requests and delivers the full block body to the validator for signing and propagation. This "header-bid-then-body" flow prevents builders from stealing profitable transaction orderings and prevents validators from viewing and stealing a block's contents before committing to it. Relays like the Flashbots Relay implement this model to create a trust-minimized environment for MEV distribution.
Centralization risks and the role of relays are a key consideration. While relays prevent certain abuses, they themselves become potential points of failure or censorship. A validator relying on a single relay only sees blocks from that relay's connected builders, which can lead to centralization of block building power. In response, the ecosystem has developed relay diversity initiatives and builder APIs like Ethereum's builder-specs (e.g., eth_sendBundle and eth_getPayload). Validators are encouraged to connect to multiple relays to access a competitive market of blocks and mitigate reliance on any single entity.
Prominent MEV-Relays
MEV-Relays are critical infrastructure that connect block builders to validators, acting as trusted intermediaries to prevent censorship and maximize validator rewards. This section details the leading operational relays.
Security & Trust Considerations
A MEV-Relay is a critical infrastructure component that sits between block builders and validators, designed to mitigate the centralization and trust risks inherent in Maximal Extractable Value (MEV) extraction. It acts as a neutral intermediary to ensure fair and secure block proposal.
Primary Function & Trust Model
A MEV-Relay's core function is to receive block proposals from builders and present them to validators. It operates on a trust-minimized model, where the validator's trust is placed in the relay's commitment to deliver the highest-paying block header it has seen. This prevents builders from censoring transactions or withholding blocks after seeing a validator's partial signature.
Censorship Resistance & OFAC Compliance
Relays are a key point of control for transaction censorship. Some relays implement OFAC compliance by filtering sanctioned addresses, while others are permissionless and censorship-resistant. This creates a critical choice for validators, impacting the network's neutrality. The relay's inclusion list policy determines which transactions can enter the block-building process.
Relay Centralization Risks
The ecosystem's reliance on a handful of dominant relays (e.g., Flashbots, bloXroute) creates centralization risks. Key concerns include:
- Single point of failure: Downtime of a major relay can disrupt block production.
- Gatekeeping power: A relay can exclude certain builders or validators.
- Coordination vectors: Relays could theoretically collude with builders or validators to manipulate the market. This risk is mitigated by validator choice and the existence of multiple competing relays.
Validator Security & PBS
Relays are a core component of Proposer-Builder Separation (PBS), a design paradigm that protects validators from MEV-related risks. By outsourcing block construction to specialized builders via a relay, validators are shielded from:
- Time-bandit attacks: Where a validator is bribed to reorg a block.
- Resource exhaustion: Complex MEV extraction can overload a validator's resources. The relay ensures the validator only sees the final, executable block header, not the building process.
Data Transparency & Auditing
To maintain trust, reputable relays provide public transparency dashboards and data feeds. Key metrics include:
- Reliability (uptime, latency)
- Censorship metrics (percentage of OFAC-compliant blocks)
- Builder market share
- Bid distribution Public data allows the community to audit relay behavior and holds them accountable to their stated policies, reducing information asymmetry.
The Future: SUAVE & Decentralization
The long-term vision is to decentralize the relay function itself. Initiatives like SUAVE (Single Unified Auction for Value Expression) aim to replace centralized relays with a decentralized, chain-native pre-confirmation network. This would eliminate trusted intermediaries, moving the relay's ordering and censorship-resistance logic into a decentralized protocol, fundamentally changing the trust assumptions.
MEV-Relay vs. Related Infrastructure
A functional comparison of an MEV-Relay with other core infrastructure components in the MEV supply chain, highlighting distinct roles and responsibilities.
| Feature / Role | MEV-Relay | Block Builder | Searcher | Validator / Proposer |
|---|---|---|---|---|
Primary Function | Trust-minimized communication channel | Constructs full block contents | Discovers & creates profitable transactions | Proposes the final block to the network |
Key Input | Validator's block header commitment | Transaction pool & searcher bundles | Public mempool & private orderflow | Best block from connected relay(s) |
Key Output | List of executable block bodies | Fully built, signed block | Transaction bundles for builders | Signed block header for chain finality |
Handles Transaction Execution | ||||
Sees Full Block Contents Before Signing | ||||
Can Censor Transactions | ||||
Typical Compensation Model | Fixed fee or pro-bono (public good) | Extracted MEV + priority fees | Portion of extracted MEV | Block reward + priority fees |
Centralization Risk Vector | Yes (Relay List) | Yes (Builder Market) | Low (Competitive) | Yes (Staking Pools) |
MEV-Relay
The evolution of MEV-Relays from basic transaction forwarding services to sophisticated, trust-minimized infrastructure is central to the future of Ethereum and other proof-of-stake blockchains.
An MEV-Relay is a specialized network service that sits between block builders and validators, facilitating the secure and efficient auction of block space for Maximal Extractable Value (MEV). It acts as a trusted intermediary, receiving encrypted transaction bundles from builders and forwarding the most profitable, valid ones to validators for inclusion in the next block. This separation of building and proposing roles is a core component of proposer-builder separation (PBS), designed to democratize access to MEV and mitigate its negative externalities like network congestion.
The evolution of relays is marked by a shift from centralized, opaque services to more decentralized and transparent models. Early relays were often operated by a single entity, creating centralization risks and potential censorship. Modern developments, such as the Ethereum Foundation's relay registry and the rise of open-source relay software like mev-boost-relay, aim to standardize protocols and foster a competitive, permissionless relay market. This progression is critical for ensuring the network's resilience and neutrality.
Key technical challenges for future relays include enhancing privacy through advanced encryption to prevent frontrunning, improving efficiency in bundle propagation to reduce latency, and implementing robust censorship resistance mechanisms. Innovations like encrypted mempools and threshold cryptography are being explored to allow validators to commit to blocks without seeing their contents until after the block is proposed, further reducing trust assumptions and validator operational risks.
The long-term future of MEV-Relays is intrinsically linked to protocol-level solutions. Ethereum's roadmap includes enshrining PBS directly into the consensus layer, a concept known as enshrined proposer-builder separation (ePBS). This would move the relay's core auction mechanism on-chain, minimizing reliance on off-chain trust and creating a more robust, verifiable, and decentralized infrastructure for MEV distribution, fundamentally shaping the economic security of the blockchain.
Frequently Asked Questions
A MEV-Relay is a critical infrastructure component that sits between block builders and validators in proof-of-stake (PoS) Ethereum, designed to mitigate the centralizing risks of Maximal Extractable Value (MEV).
A MEV-Relay is a network node that acts as a trusted intermediary between searchers (who submit MEV bundles) and block builders (who construct candidate blocks), preventing builders from stealing the MEV strategies within the bundles they receive. It works by receiving encrypted transaction bundles from searchers and forwarding them to multiple builders. The builders construct blocks containing these bundles but cannot decrypt the transactions until they have committed to including them in a block they propose to a validator. This process, known as commit-reveal, ensures builders cannot front-run or copy the profitable strategies before including them.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.