Validator Guide

​

Why Participate?

Participation of L1 validators in the mev-commit protocol increases the credibility of preconfs made through mev-commit and consequently their value. Due to increased preconf values, providers have additional value to bid in the mev-boost auction, thus driving up the total revenue a proposer will get.

​

Requirements

1. An operational L1 validator node.
2. An operational mev-boost or other sidecar.
3. 3 ETH worth of stake or restake per validator, or 1,000 ETH worth per operator entity.

By opting-in to the mev-commit protocol as a validator in one of the three forms described, you agree to only use opted-in relays. These opted-in relays will only forward mev-boost bids from addresses that have registered with the mev-commit provider registry, such that providers can be slashed in case of a protocol violation. We generally don’t anticipate validator slashing events, as this allows validators to passively opt-in to mev-commit, letting block builders and relays do the work.

​

Supporting Relays

If you are a relay looking to join the mev-commit network please visit our Relays page to get more information. Proposers who fallback to local block production, from either a fault in the mev-boost software or a lack of economically viable block bids, will not be slashed. See flashbots docs for more on this scenario. The protocol may in the future slash for abuse of this local fallback mechanism.

​

Choose Your Opt-In Method

Note each validator pubkey should only opt-in using one of the three methods described below.

​

Protocol Design

To learn more about the protocol design for any of the registries, see their respective READMEs:

• MevCommitMiddleware
• MevCommitAVS
• VanillaRegistry

To query the on-chain parameters of any registry (on mainnet or Hoodi), run an example forge script like this.