Skip to main content

​
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 the mev-boost relay set they run for commitment attribution. mev-commit no longer maintains a curated “supporting relays” list — opted-in validators can use any relay, and mev-commit’s oracle attributes commitments via standard proposer_payload_delivered data.

​
Risks

While mev-commit is generally not set up to slash validators, validators opting into the mev-commit protocol should be aware of the following risks:
  • Trusted Relay block delivery: Relays could break their trust and communicate blocks that do not abide by existing commitments. Commitment accountability sits on the provider side — providers that fail to honor commitments are slashed regardless of which relay delivered the block.

​
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. Stay tuned for more updates on this.

​
More Resources

Why Should Validators Opt In?

FAQ on validator incentives, earnings, and the opt-in rationale.