mev-commit Testnet

Live on Holesky Testnet, 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 to be tested on the mev-commit testnet.

Links and Connection Details

Services links

Service	Link
Testnet RPC	https://chainrpc.testnet.mev-commit.xyz/
Bootnode endpoint	https://bootnode.testnet.mev-commit.xyz/
Block explorer	http://explorer.testnet.mev-commit.xyz/blocks
Faucet	http://faucet.testnet.mev-commit.xyz/

Contract Addresses

Contract	Address
BidderRegistry	0x7ffa86fF89489Bca72Fec2a978e33f9870B2Bd25
ProviderRegistry	0x4FC9b98e1A0Ff10de4c2cf294656854F1d5B207D
PreConfCommitmentStore	0xCAC68D97a56b19204Dd3dbDC103CB24D47A825A3
Oracle	0x6856Eb630C79D491886E104D328834643B3F69E3
BlockTracker	0x2eEbF31f5c932D51556E70235FB98bB2237d065c

Infrastructure

Primev will maintain a testnet consisting of the mev-commit chain, oracle service, and bridge to Holesky.

Differences Between the Testnet and Mainnet Environments

Testnet bridging ether to/from Holesky, whereas mainnet mev-commit chain will bridge using mainnet ether. Commitments are also written to the settlement chain in plaintext, whereas mainnnet will include private commitments.

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.