Relay Integration Guide
Overview
Enabling mev-commit on your relay is simple and requires minimal changes to your existing setup.
This guide explains how to integrate your relay with mev-commit.
Your relay will check if the current slot’s validator has opted into mev-commit:
- If they haven’t opted in, your relay works normally:
- If they have opted in, your relay only accepts blocks from mev-commit builders:
To implement this, your relay needs to track two things:
- Provider Registry: Lists opted-in builders and their BLS keys
- Validator Registry: Shows which validators have opted into mev-commit
Quick Start
View the Example Implementation
Test and Deploy
Test filtering behavior on Holesky:
- Register a test builder
- Submit test bids
- Verify correct block filtering
Register Your Relay
- Add your relay to our supporting relays list
- Provide connection details for validators
- Contact the Primev team to coordinate validator outreach
You have now successfully integrated your relay with mev-commit.
Implementation Details
What Contracts to Monitor
To track which validators have opted into mev-commit, you’ll want to monitor the following contracts:
Ethereum L1
| Network | Contract | Address |
|---|---|---|
| Mainnet | Validator Opt In Router | |
| Holesky | Validator Opt In Router |
mev-commit Chain
| Network | Contract | Address |
|---|---|---|
| Mainnet | Provider Registry | |
| Testnet | Provider Registry |
By monitoring these contracts, you can determine which validators and providers have opted into mev-commit and ensure compliance with the protocol.
How to Query the Provider Registry
The mev-commit provider registry contract maintains the list of authorized providers such as block builders. You can query this contract to validate builder addresses.
Contract Details:
| Network | Address |
|---|---|
| mev-commit chain mainnet | |
| mev-commit chain testnet |