Relay Guide

Relays play an important role in the mev-commit ecosystem to uphold validator commitments. Validators are passively opting in to the network, and configuring their mev-boost relays to the ones that have opted in to mev-commit.

Opting into mev-commit as a relay means that you sign up to deliver mev-boost bids only from builder addresses that have registered with mev-commit. This is necessary as it acts as a sybil resistance mechanism, disallowing block builders from making commitments but building a block under a different builder key that mev-commit would not be able to penalize. In this context, ‘filtering’ refers to the relay’s role in screening and validating builder addresses, ensuring that only those registered with mev-commit are allowed to submit bids, following the protocol.

Information about the providers (entities like builders who commit on our network) is stored the provider registry hosted on the mev-commit chain. You can interact with the registry contract at address: .

// Import the ethers library
const ethers = require("ethers");

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

// Define the contract address and ABI
const providerRegistryAddress = "0x4FC9b98e1A0Ff10de4c2cf294656854F1d5B207D";
const abi = [
    "event ProviderRegistered(address indexed provider, uint256 stakedAmount, bytes blsPublicKey)"
];

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

// Function to retrieve the list of registered providers
async function getRegisteredProviders() {
    // Create a filter for the ProviderRegistered event
    const filter = contract.filters.ProviderRegistered();

    // Query the contract for the ProviderRegistered events
    const events = await contract.queryFilter(filter);

    // Map the events to get the list of provider bls public keys
    const providers = events.map(event => event.args.blsPublicKey);

    return providers;
}

// Call the function and log the result
getRegisteredProviders().then(providers => {
    console.log("Registered Providers:", providers);
}).catch(error => {
    console.error("Error:", error);
});

Registered Providers: [
  '0x4e9c5b21bb1df120a7000fac8e3b1978bc308d28b54bbeae76eff010d8d8f83d785adc4141faf179715f550088becd7f',
  '0x2e6b986435137b88685d8a2783c46ec9a68958bbb3f50b09a538954942c0f9066493d35b3e341a059a507d66d4545c23',
  '0x43c615787576375f2c7db9c03c8899bab545881e373a963873b0f10c00faa3da57c7c7ecc1915809c651bb40c055b22e',
  ...
]

Relays need to look out for mev-commit opted-in proposer addresses, and only deliver block builder bids from builder addresses that are registered with mev-commit when it’s that proposer’s turn. See Querying for Proposers to see how you can check whether an upcoming proposer is opted in to mev-commit or not.

Once you’ve configured your relay to deliver blocks with mev-commit commitments, create a PR to this docs repo to add your relay to the supporting relays list. This will let validators know that they can add your relay as they opt-in to mev-commit. You should also let the Primev team know so we can further engage with validators to make sure they use your relay as well.