​
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:
mev-commit relay diagram
  • If they have opted in, your relay only accepts blocks from mev-commit builders:
mev-commit validator relay diagram
To implement this, your relay needs to track two things:
  1. Provider Registry: Lists opted-in builders and their BLS keys
  2. Validator Registry: Shows which validators have opted into mev-commit

​
Quick Start

1

View the Example Implementation

​
Mainnet

​
Testnet

2

Test and Deploy

Test filtering behavior on Hoodi:
3

Register Your Relay

  1. Add your relay to our supporting relays list
  2. Provide connection details for validators
  3. 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

NetworkContractAddress
MainnetValidator Opt In Router
HoodiValidator Opt In Router

​
mev-commit Chain

NetworkContractAddress
MainnetProvider Registry
TestnetProvider 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:
NetworkAddress
mev-commit chain mainnet
mev-commit chain testnet
You can retrieve all registered providers using the following script:
// Import the ethers library
const ethers = require("ethers");

// Define the provider using the RPC URL
const provider = new ethers.JsonRpcProvider("https://chainrpc.mev-commit.xyz/");

// Define the contract address and ABI
const providerRegistryAddress = "0xb772Add4718E5BD6Fe57Fb486A6f7f008E52167E";
const abi = [
    "event ProviderRegistered(address indexed provider, uint256 stakedAmount)",
    "function isProviderValid(address provider) public view",
    "function getBLSKeys(address provider) external view returns (bytes[])"
];

// Create a new contract instance
const contract = new ethers.Contract(providerRegistryAddress, abi, provider);

// Function to retrieve BLS keys grouped by valid provider address
async function getRegisteredProviders() {
    const filter = contract.filters.ProviderRegistered();
    const events = await contract.queryFilter(filter);
    let totalKeys = 0;

    const providerMap = {};

    for (const event of events) {
        const providerAddress = event.args.provider;

        try {
            //This will fail if the provider isn't valid
            await contract.isProviderValid(providerAddress);

            const blsKeys = await contract.getBLSKeys(providerAddress);

            // Convert each key to hex string for any future usage
            providerMap[providerAddress] = blsKeys.map(key => ethers.hexlify(key));
            totalKeys += blsKeys.length
        } catch (error) {
            // Skip invalid providers or failed fetches
        }
    }

    console.log("Total registered keys: ", totalKeys);
    return providerMap;
}

// Run and log providers with their BLS keys
getRegisteredProviders()
    .then(providerMap => {
    console.log("Valid providers and their BLS keys:");
        for (const [address, blsKeys] of Object.entries(providerMap)) {
            console.log(`\nProvider: ${address}`);
            blsKeys.forEach((key, index) => {
            console.log(`  Key ${index + 1}: ${key}`);
            });
        }
    })
    .catch(error => {
        console.error("Error fetching providers:", error);
    });
The output will contain the number of all registered keys and a list of providers with their registered BLS public keys.
Total registered keys:  23
Valid providers and their BLS keys:

Provider: 0x...
  Key 1: 0x...

Provider: 0x...
  Key 1: 0x...

Provider: 0x...
  Key 1: 0x...
  Key 2: 0x...
  Key 3: 0x...

...

​
Steps for v1.2 upgrade

The v1.2 upgrade to the mev-commit protocol will launch on mainnet in September 2025. For relays to enable this upgrade, the following will be required:
  • Relays must change the provider registry address used to query provider registrations. The new address will be available soon, and will be available at https://contracts.mev-commit.xyz/ or the mainnet docs page.
  • Relays must be able to handle the mev-commit chain starting from genesis. That is, the new provider registry contract address should be re-queried from block zero.
  • Any code relying on chain ID or block number values returned by the mev-commit chain RPC url must be able to handle those values changing.
Please feel free to reach out to us on telegram if you have any questions.