cast
, with the following command:foundryup
to update to the latest versions of Foundry’s suite of tools:
forge
, cast
, anvil
, and chisel
:Linux x86_64
or Darwin arm64
, depending on your system.uname -sm
yields Linux x86_64
, opt for mev-commit_Linux_x86_64.tar.gz
.
Download, then extract the binary into your preferred root directory to continue with setup.You can use the following command which automatically downloads and extracts the appropriate
mev-commit binary for your system into your home directory:🕵️♂️ Recommended: Verify the checksum
Grab the checksum
Verify
--bootnodes
This should point to the bootnode for the Primev testnet network.--settlement-rpc-endpoint
This should point to the Primev Settlement Chain RPC endpoint. At present this is managed by the Primev team.--peer-type
flag can be used to run a provider
or bidder
node.
❗ The default contract addresses point to the Primev testnet at the moment. All the options can be provided using a YAML config file or environment variables as described in the above help output.
❗ The mev-commit node, when started for the first time will create a private key for the node at ~/.mev-commit/key
. This is a plain-text key. In order to store encrypted keys, users need to use the keystore. This can be configured using the --keystore-path
and --keystore-password
.
❗ In order to run a provider node, the machine needs to be publicly accessible. Also, the mev-commit node will have to be configured with the public IP of the node using the nat-addr
parameter.