Validator Guide
Opt into mev-commit with ease. This guide covers everything you need to do to passively interact with the mev-commit protocol as a validator.
Opting-in as a Validator
Participation of L1 validators in the mev-commit protocol is crucial as it enhances the integrity of commitments and ensures their enforcement. This document details the steps required to join mev-commit as a Holesky validator.
As a Holesky validator opting into the mev-commit protocol, ensure your mev-boost client only connects to mev-commit opted-in relays to avoid slashing for proposing blocks without delivering commitments.
Requirements
By opting-in to the mev-commit protocol as a Holesky validator in any of the three forms described, you agree to use the opted-in relays who will filter block builder bids to the addresses that have registered with mev-commit provider registry so they can be slashed in case of protocol violation. This allows validators to passively opt-in to mev-commit and let block builders and relays do the work.
Supporting Relays:
Relay | Docs |
---|---|
Titan | docs.titanrelay.xyz |
Aestus | holesky.aestus.live |
We expect all known relays to support opting-in to mev-commit within a few months of being live on mainnet. 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
Eigenlayer Restaking
Native restaking with the MevCommitAVS
Symbiotic Restaking
ERC20 restaking with the MevCommitMiddleware
Simple Staking
”Vanilla” staking ETH with the VanillaRegistry
Relevant contract addresses can be found on the testnet page.
Eigenlayer Restaking Option
If you plan to bulk opt-in a large number of validators, check out the Eigenlayer Operator Registration guide.
Otherwise, an individual validator entity can delegate to an existing registered Operator.
A native-restaking enabled validator opting in to mev-commit requires two high level steps:
- The validator must delegate (via eigenlayer core) their native stake to an Operator who’s registered with the mev-commit AVS. These can be found on the mev-commit AVS Eigenlayer dashboard. If your existing delegated operator is not registered with mev-commit, you have the option to change your delegation.
- The validator must separately be registered with the mev-commit AVS, confirming their attestation to follow the rules of the protocol.
Step 2 will be facilitated by the MevCommitAVS.registerValidatorsByPodOwners
function. Frontend instructions are coming soon.
Eigenlayer LST Restaking
For validator entities to opt-in to mev-commit through Eigenlayer, they must follow the above steps involving native restaking. In addition to this, any LST restaker is able to over-collateralize validators who’ve already registered with the MevCommitAVS. Rewards and/or points for this method of over-collateralization are TBD. See more here.