Manual Node Setup
Below, you’ll find a guide tailored for those who prefer a more customized installation approach.
Install cast
We use the cast CLI tool for making Ethereum RPC calls.
If it’s not already installed on your system, you can set up the entire Foundry toolchain, including cast
, with the following command:
After installation, execute foundryup
to update to the latest versions of Foundry’s suite of tools:
forge
, cast
, anvil
, and chisel
:
For detailed guidance, refer to the official Foundry Book installation instructions.
Check your CPU architecture
Run the following command which will identify your OS, and chip architecture:
This command will output something like Linux x86_64
or Darwin arm64
, depending on your system.
Get the mev-commit binary
Navigate to the mev-commit repo
and select the mev-commit binary tailored to your system.
For example, if 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:
Starting up your Node
Execute the script to initiate your node, selecting either a bidder or provider configuration based on your role in the network.
Bidders
Providers
--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.
❗ The --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.