Ensure you have completed the steps from the quickstart guide in a separate terminal. This will set up your environment and spin up a bidder node.
Getting deposits and bidder balance
To query all deposits and your bidder’s balance on the mev-commit chain:❯_ terminal
❯_ typical response
❯_ terminal
❯_ typical response
Deposit represents the funds in the bidder’s account that can be used to submit bids on the mev-commit p2p-network and settled on-chain.
Deposit manager
It’s recommended that bidders leverage the deposit manager to deposit, and automate ongoing re-deposits to specific providers. The deposit manager is an on-chain contract that a bidder account can enable by “setting their code” to the implementation using EIP-7702. After enabling the deposit manager, a bidder’s deposits are automatically replenished from the bidder’s EOA balance during the preconf settlement process, according to target deposit amounts configured by the bidder. A target deposit is the desired amount of funds that a bidder wants to be deposited for a specific provider. Bidders should set their target deposits to the maximum cumulative amount of ETH they would ever bid to a provider with respect to a single L1 block. If you followed the quickstart guide exactly, your bidder node will already have the deposit manager enabled. To confirm:Get deposit manager status
❯_ terminal
❯_ typical response
Enabling deposit manager on boot up (recommended)
The easiest way to enable the deposit manager is by setting two flags/environment variables upon starting your bidder node:❯_ terminal
MEV_COMMIT_ENABLE_DEPOSIT_MANAGER
and MEV_COMMIT_TARGET_DEPOSIT_AMOUNT
environment variables.
This is the method used by the quickstart guide.
Enabling deposit manager through API
To enable the deposit manager through API, use the following command:❯_ terminal
❯_ typical response
Setting target deposits
Then to set target deposits customized to each provider:❯_ terminal
❯_ typical response
set_target_deposits
endpoint.
Disable deposit manager
To disable the deposit manager call:❯_ terminal
❯_ typical response
Withdraw deposited funds
To withdraw funds from your deposit to a specific provider, use the following command:❯_ terminal
❯_ typical response
❯_ typical response
Health
The health endpoint checks whether the bidder node is receiving events from mev-commit chain. This command is useful to determine whether the bidder node has become out of sync.❯_ terminal
Topology
The topology endpoint can be used to check which provider nodes the bidder node is connected to. It’ll also display yourEthereum Address
and Peer Type
.
❯_ terminal
Querying for proposers API
This API is enabled by default, the following environment variables could be set when launching a mev-commit client:MEV_COMMIT_VALIDATOR_ROUTER_ADDR
MEV_COMMIT_BEACON_API_URL
MEV_COMMIT_L1_RPC_URL
❯_ terminal
❯_ terminal
❯_ terminal
- The next block proposer has opted in to the mev-commit protocol (
validator_opted_in
) - A new epoch begins, providing a list of all opted-in validators for that epoch (
epoch_validators_opted_in
)
Configuring custom provider sets
Users can also set-up a specific subset of provider nodes in order to send their bids. By default the mev-commit bidder node will send bids to all the available and staked providers. However, if the user wants only a specific subset of providers to be able to see their bids, the can use the--provider-whitelist
option to set it up. The list should contain the ethereum wallet addresses of the provider nodes.
Mainnet
❯_ terminal
Testnet
❯_ terminal