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.
Configure mev-boost to only connect to mev-commit opted-in relays.
Configure mev-boost with min-bid 0.
As a validator opting into the mev-commit protocol, ensure your mev-boost client is configured with min-bid 0 and only connects to mev-commit opted-in relays to avoid slashing for proposing blocks without delivering commitments.
By opting-in to the mev-commit protocol as a validator in one of the three forms described, you agree to not self build blocks by setting the min-bid parameter to 0 and 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. These two steps ensure that the validator only proposes blocks from registered block builders such that these builders 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.
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.
