1

Launch mev-commit Bidder Node

​
Mainnet

❯_ bidder
curl -L -o launchmevcommit launch.mev-commit.xyz; chmod +x launchmevcommit; ./launchmevcommit --node-type bidder

​
Testnet

❯_ bidder
 curl -L -o launchmevcommit launch.mev-commit.xyz; chmod +x launchmevcommit; DOMAIN="testnet.mev-commit.xyz" ./launchmevcommit --node-type bidder
2

Fund Your Account

In order to fund your account, you’ll need to bridge ETH to the mev-commit chain. The easiest way to do this is through our web interface:

  1. Visit mev-commit.xyz/bridge
  2. Connect your wallet (MetaMask or WalletConnect supported)
  3. Select Ethereum as the source chain and mev-commit as the destination
  4. Enter the amount of ETH you want to transfer
  5. Click “Bridge” and approve the transaction

Wait for the bridge transaction to complete (approximately 15 minutes for L1 finality). You can see detailed instructions in our Bridge UI guide.

For automated or programmatic bridging, you can use our CLI tool by first confirming your operating system and architecture by running uname -sm then downloading the appropriate bridge user CLI binary from the releases page.

Or download the 1.1.0 bridge CLI directly from the links below:

The CLI application provides two sub-commands to bridge to and from the settlement chain. For more details go the the bridge documentation.

Make sure to specify the newly generated account address from the previous step as the destination address for the bridge command.
❯_ example
./user-cli bridge-to-settlement --account-key <PRIVATE KEY of source account for funds> --dest-addr <Address to fund on mev-commit chain> --amount 1000000000000000000
3

Send a Bid

Open a new terminal window to send a bid and receive commitments from providers. Run the following command:

❯_ example
curl -X POST http://localhost:13523/v1/bidder/bid \
-d '{
    "rawTransactions": ["0x02f8db82426882010c8410433624841043362f8303425094ea593b730d745fb5fe01b6d20e6603915252c6bf87016e03ce313800b864ce0b63ce0000000000000000000000000e94804eaa3c4c5355992086647f683f6f41ef1f000000000000000000000000000000000000000000000000000150e0786cc000000000000000000000000000000000000000000000000000000000000004e378c001a0ece6d13b20247abdc07d669c9186ee5a1ac9601db8c98a3323024ab299cb6662a01c20680efe4e0bb48a3a936b5ab27c741819f0ac567b12b34b230004b20b78a0"],
    "amount": "<amount in wei>",
    "blockNumber": <integer l1blocknumber>,
    "decayStartTimestamp": <timestamp milliseconds>,
    "decayEndTimestamp": <timestamp milliseconds>,
    "revertingTxHashes": []
}'

You can change the values in the fields amount, blockNumber, decayStartTimestamp, decayEndTimestamp and revertingTxHashes as desired. The rawTransactions field contains hexadecimal string of the RLP encoded raw transaction payloads, include raw transaction payloads in your bid in the atomic sequence in which they need to be placed in the block. Only one out of txHashes or rawTransactions need to be sent in a bid.

Make sure your bid amount is sufficiently high for the commitment you’re requesting, and your target L1 block number is accurate. It’s up to the providers to commit to your bid, so try to ensure a commitment is feasible to your bid by its construction. Selecting a target block of n+1 where n is the current block number generally makes it easy to receive a commitment for standard bid amounts.

Congrats, you just sent your first L1 preconfirmation bid! You should be receiving commitments nearly instantly.

Alternatively you can send a bid using the txHashes field instead of rawTransactions to refer to a transaction a provider has in their own environment using its hash. This method also allows you to bid on others’ behalf using their transaction hashes.

❯_ example
curl -X POST http://localhost:13523/v1/bidder/bid \
-d '{
    "txHashes": ["0549fc7c57fffbdbfb2cf9d5e0de165fc68dadb5c27c42fdad0bdf506f4eacae"],
    "amount": "<amount in wei>",
    "blockNumber": <integer l1blocknumber>,
    "decayStartTimestamp": <timestamp milliseconds>,
    "decayEndTimestamp": <timestamp milliseconds>,
    "revertingTxHashes": []
}'
Make sure to check System Requirements to better understand what is needed to run mev-commit without any interruptions. If you want to perform a manual setup and learn details, please skip to the manual start mev-commit section.

​
Bidder CLI application

In order to make it simpler for users to interact with the bidder node, the team has also created a CLI application which aims to provider a simpler UX to send transactions or bids to the mev-commit network. You can check the bidder CLI docs for more details.

​
Preconf Bot Example with Docker

Ready to work preconf bot examples can be found here and ready to be dockerized. Additionally, the dockerized bidder node example repository can be found here.