Skip to main content
Live with Holesky, mev-commit allows bidders and providers to engage in execution service bids and commitments. Preconfirmations, the first use case for real-time bids and commitments, are available with mev-commit.

Core Contract Addresses (Mev-commit chain)

ContractAddress
BidderRegistry0x401B3287364f95694c43ACA3252831cAc02e5C41
ProviderRegistry0xf4F10e18244d836311508917A3B04694D88999Dd
PreconfManager0x9433bCD9e89F923ce587f7FA7E39e120E93eb84D
Oracle0x0a3ad886AEfd3bA877bcB23E171e0e2a375806a0
BlockTracker0x7538F3AaA07dA1990486De21A0B438F55e9639e4

Validator Registry Contract Addresses (Holesky)

ContractAddress
ValidatorOptInRouter0x251Fbc993f58cBfDA8Ad7b0278084F915aCE7fc3
VanillaRegistry0x87D5F694fAD0b6C8aaBCa96277DE09451E277Bcf
MevCommitAVS0xEDEDB8ed37A43Fd399108A44646B85b780D85DD4
MevCommitMiddleware0x79FeCD427e5A3e5f1a40895A0AC20A6a50C95393

Other addresses (Holesky)

EntityAddress
Mev-commit (Symbiotic) Network Address0x4535bd6fF24860b5fd2889857651a85fb3d3C6b1

How can users provide feedback or report issues encountered on the testnet?

Users can open an issue on the GitHub repository that is associated with any issue they encounter. They can also tag @primev_xyz on Twitter, or reach out to us to join a Telegram group for early power users.

Testnet System Requirements

Please refer to the System Requirements section here.