Validator considerations

​

Trust Assumptions

Opting into the mev-commit protocol signals from a validator that they:

• Trust correctness of execution from the mev-commit chain. See mev-commit chain for more information.
• Trust correctness of slashing transactions residing from the Primev operated mev-commit-oracle service.
• Trust at least one mev-commit opted in relay. The Titan Holesky relay is the only such relay at this time, see the Titan Holesky Relay here.
• Attest they will follow the rules of the protocol given the above trust assumptions. This currently entails only proposing blocks that come from a mev-commit opted in relay.

​

Risks

Validators opting into the mev-commit protocol should be aware of the following risks:

• Relay block delivery: Relays could communicate blocks that do not abide by existing commitments. This would lead to slashing of the validator.
• Failure to propose block: Validators could fail to propose a block for a slot that has preconf commitments. This would lead to slashing of the validator if there are existing commitments

​

Future plans

While mev-commit AVS is passive and doesn’t require operators to run any software today, Primev is researching means to decentralize centralized components of the mev-commit stack through bundling them into an AVS. Stay tuned for more updates on this.