Mev-commit Mainnet

Live with Ethereum Mainnet, 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.

​

Links and Connection Details

​

Services links

​

Core Contract Addresses (mev-commit chain)

Contract	Address
BidderRegistry	0x948eCD70FaeF6746A30a00F30f8b9fB2659e4062
ProviderRegistry	0x1C2a592950E5dAd49c0E2F3A402DCF496bdf7b67
PreconfManager	0xa254D1A10777e358B0c2e945343664c7309A0D9d
Oracle	0xCd27C2Dc26d37Bb17686F709Db438D3Dc546437C
BlockTracker	0xCd27C2Dc26d37Bb17686F709Db438D3Dc546437C

​

Bridge Gateway (mev-commit chain)

Contract	Address
SettlementGateway	0xFaF6F0d4bbc7bC33a4b403b274aBb82d0E794202

​

Bridge Gateway (L1 Ethereum)

Entity	Address
L1Gateway	0x567f0f6d4f7A306c9824d5Ffd0E26f39682cDd7c

​

L1 Validator Registries

Contract	Address Type	Address
MevCommitAVS	Proxy	0xBc77233855e3274E1903771675Eb71E602D9DC2e
	Implementation	0x5A68216faE665dF4650597B7472101Bb1b66C208
VanillaRegistry	Proxy	0x47afdcB2B089C16CEe354811EA1Bbe0DB7c335E9
	Implementation	0x59fBE4CC4CA974e98300F41Ac661f7204F0c3fCd
ValidatorOptInRouter	Proxy	0x821798d7b9d57dF7Ed7616ef9111A616aB19ed64
	Implementation	0x585963E61dd3943bAe02F4f2dBaE0f9EDBa842Af

All contract calls should be made through the proxy contracts. Implementations are listed for transparency, where verified contract code can be viewed.

​

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.

​

Mainnet System Requirements

Please refer to the System Requirements section here.