| title | mev-commit Testnet |
|---|---|
| sidebarTitle | 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.
| Service | Link |
|---|---|
| Bootnode endpoint | https://bootnode.testnet.mev-commit.xyz/ |
| Block explorer | http://explorer.testnet.mev-commit.xyz/blocks |
| Contract | Address |
|---|---|
| BidderRegistry | 0xa86a41b57Fb73f9118F84847574517258d29eAD0 |
| ProviderRegistry | 0x5960774AD41D03DAB4916a30bD2190f8b3b3b4b2 |
| PreConfCommitmentStore | 0x7D1a4707e573D260581f3AB3f90f697Ab03fC6Dd |
| Oracle | 0xFA626Ad00244CC08e4E34A10d2d1Aa1E930AA6dC |
| Whitelist | 0x57508f0B0f3426758F1f3D63ad4935a7c9383620 |
Primev will maintain a testnet consisting of the mev-commit chain, oracle service, and bridge to Holesky.
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.
Bids aren't encrypted on the testnet yet, meaning all exchanges are publicly visible. There is also no differentiator between a timely or a late commitment as of now. Both of these will change with our upcoming testnet milestone.
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.
Please refer to the System Requirements section [here.]/developers/system-requirements)