> For the complete documentation index, see [llms.txt](https://docs.eridian.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eridian.xyz/ethereum-dev/infrastructure/client-software/mev-boost/installation.md). # Installation * [Create Aliases](#create-aliases) * [Firewall Configuration](#firewall-configuration) * [MEV Boost - Install](#mev-boost-install) * [MEV Boost - Configure Service](#mev-boost-configure-service) * [MEV Boost - Update Scripts](#mev-boost-update-scripts) ### Create Aliases ```bash echo "alias mev-log='journalctl -f -u mevboost.service -o cat | ccze -A'" >> ~/.bashrc echo "alias mev-start='sudo systemctl start mevboost.service'" >> ~/.bashrc echo "alias mev-stop='sudo systemctl stop mevboost.service'" >> ~/.bashrc echo "alias mev-restart='sudo systemctl restart mevboost.service'" >> ~/.bashrc echo "alias mev-status='sudo systemctl status mevboost.service'" >> ~/.bashrc echo "alias mev-config='sudo vim /etc/systemd/system/mevboost.service'" >> ~/.bashrc echo "alias mev-enable='sudo systemctl enable mevboost.service'" >> ~/.bashrc echo "alias mev-disable='sudo systemctl disable mevboost.service'" >> ~/.bashrc echo "alias mev-update='~/mev-update.sh'" >> ~/.bashrc source ~/.bashrc ``` ### MEV Boost - Install Build the latest version of `MEV Boost`. ```bash MEV_VERSION_COMMIT_HASH= # e.g.441fc16 cd ~ git clone https://github.com/flashbots/mev-boost.git cd ~/mev-boost git checkout ${MEV_VERSION_COMMIT_HASH} make build ``` Move the compiled `MEV Boost` build to a new directory. ```bash sudo cp ~/mev-boost/mev-boost /usr/local/bin ``` Create `MEV Boost` user and directory. ```bash sudo useradd --no-create-home --shell /bin/false mevboost sudo chown -R mevboost:mevboost ~/mev-boost ``` ### MEV Boost - Configure Service Configure `MEV Boost` service using the command line flags. ```bash sudo vim /etc/systemd/system/mevboost.service ``` {% tabs %} {% tab title="/etc/systemd/system/mevboost.service" %} {% code title="/etc/systemd/system/mevboost.service" %} ```bash [Unit] Description=mev-boost Wants=network-online.target After=network-online.target [Service] Type=simple User=mevboost Group=mevboost Restart=always RestartSec=5 Environment=NETWORK= # E.g. mainnet or holesky Environment=ADDR_IP= # E.g. 0.0.0.0 Environment=ADDR_PORT= # Default: 18550 Environment=MIN_BID= # E.g. 0.01 Environment=RELAYS= # E.g. "https://@relay.ultrasound.money" ExecStart=/usr/local/bin/mev-boost \ -${NETWORK} \ -addr ${ADDR_IP}:${ADDR_PORT} \ -min-bid ${MIN_BID} \ -relay-check \ -relays ${RELAYS} [Install] WantedBy=multi-user.target ``` {% endcode %} {% endtab %} {% tab title="MEV Boost Flags Explained" %}
FlagDescription
/usr/local/bin/mev-boostStarts MEV Boost.
-${NETWORK}Specifies the target network.
-addrSet listening port.
-min-bidSets the minimum bid that needs to be offered to accept a block from the relay.

If no offer is higher than the min-bid then the validator will build its own block locally.
-relay-checkMEV Boost pings the relays to check they are still alive.
-relaysComma separated list of relay addresses.
{% endtab %} {% endtabs %} Start the service and check it's working as expected. {% tabs %} {% tab title="Command Aliases" %} ```bash daemon-reload # Reload any changes made to the mevboost.service mev-enable # Enable the mevboost.service mev-start # Start the mevboost.service mev-status # View the status of the mevboost.service mev-log # View the mevboost.service logs ``` {% endtab %} {% tab title="Full Commands" %} ```bash sudo systemctl daemon-reload # Reload any changes made to the mevboost.service sudo systemctl enable mevboost.service # Enable the mevboost.service sudo systemctl start mevboost.service # Start the mevboost.service sudo systemctl status mevboost.service # View the status of the mevboost.service sudo journalctl -f -u mevboost.service -o cat | ccze -A # View the mevboost.service logs ``` {% endtab %} {% endtabs %} ### MEV Boost - Update Scripts Create `MEV Boost` update script. ```bash vim ~/mev-update.sh ``` {% code title="\~/mev-update.sh" %} ```bash #!/bin/bash set -e while true; do read -p "Are you sure you want to update MEV Boost? (Y/N) " yn case $yn in [Yy]* ) break;; [Nn]* ) exit;; * ) echo "Please answer Y or N.";; esac done cd ~/ sudo rm -rf mev-boost git clone https://github.com/flashbots/mev-boost.git cd mev-boost read -p "Enter the commit hash you want to checkout: " commit_hash git fetch git checkout $commit_hash echo echo "*******************" echo "Making MEV Boost..." echo "*******************" make build # Check if mevboost.service exists and is running service_was_running=0 if sudo systemctl is-active --quiet mevboost.service; then service_was_running=1 echo "*********************" echo "Stopping MEV Boost..." sudo systemctl stop mevboost.service fi echo "Replacing previous version..." sudo rm /usr/local/bin/mev-boost sudo cp ~/mev-boost/mev-boost /usr/local/bin # Only start mevboost.service if it was running originally if [ $service_was_running -eq 1 ]; then echo "Restarting MEV Boost..." echo "***********************" sudo systemctl start mevboost.service fi ``` {% endcode %} Make the script executable. ```bash chmod u+x ~/mev-update.sh ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eridian.xyz/ethereum-dev/infrastructure/client-software/mev-boost/installation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.