Mev-boost client Installation guide

Install client

• Find the latest stable version at Github

  Write latest stable Mev-boost version from https://github.com/flashbots/mev-boost/releases:

• Download Mev-boost version 1.9 from GitHub

  cd ~/downloads
  				curl -LO https://github.com/flashbots/mev-boost/releases/download/v1.9/mev-boost_1.9_linux_amd64.tar.gz

  Get hash of the downloaded file

  sha256sum mev-boost_1.9_linux_amd64.tar.gz

  And compare it to content of https://github.com/flashbots/mev-boost/releases/download/v1.9/checksums.txt.

• Unpack mevboost

  tar xvf mev-boost_1.9_linux_amd64.tar.gz

  Remove downloaded + useless unpacked files

  rm LICENSE README.md mev-boost_1.9_linux_amd64.tar.gz

• Copy mev-boost client to /usr/local/bin

  sudo cp ~/downloads/mev-boost /usr/local/bin

• Create a system user and system service for running Mev-boost

  System user

  sudo useradd --system --no-create-home --shell /bin/false mevboost

  Open Systemd unit file for mevboost

  sudo nano /etc/systemd/system/mevboost.service

  And copy sample configuration below into it.

  [Unit]
  				Description=MEV-Boost Service for Ethereum Mainnet
  				Wants=network-online.target
  				After=network-online.target
  				Documentation=https://stakers.space/mev-boost
  				
  				[Service]
  				User=mevboost
  				Group=mevboost
  				Type=simple
  				Restart=always
  				RestartSec=5
  				ExecStart=/usr/local/bin/mev-boost \
  				  -mainnet \
  				  -min-bid 0.03 \
  				  -relay-check \
  				  -addr 127.0.0.1:18550 \
  				  -relay https://0xac6e77dfe25ecd6110b8e780608cce0dab71fdd5ebea22a16c0205200f2f8e2e3ad3b71d3499c54ad14d6c21b41a37ae@boost-relay.flashbots.net \
  				  -relay https://0xa1559ace749633b997cb3fdacffb890aeebdb0f5a3b6aaa7eeeaf1a38af0a8fe88b9e4b1f61f236d2e64d95733327a62@relay.ultrasound.money \
  				  -relay https://0xa15b52576bcbf1072f4a011c0f99f9fb6c66f3e1ff321f11f461d15e31b1cb359caa092c71bbded0bae5b5ea401aab7e@aestus.live \
  				  -relay https://0x8b5d2e73e2a3a55c6c87b8b6eb92e0149a125c852751db1422fa951e42a09b82c142c3ea98d0d9930b056a3bc9896b8f@bloxroute.max-profit.blxrbdn.com \
  				  -relay https://0x8c7d33605ecef85403f8b7289c8058f440cbb6bf72b055dfe2f3e2c6695b6a1ea5a9cd0eb3a7982927a463feb4c3dae2@relay.wenmerge.com
  				
  				[Install]
  				WantedBy=multi-user.target

  Note: Replace ralyes for your preferred rallyes from MEV relay list

  Mev-boost is not available for Gnosis chain

  Restart daemon

  sudo systemctl daemon-reload

• Start Mev boost service

  sudo systemctl start mevboost

• Monitor Mev-boost running

  systemctl status mevboost

  journalctl -fu mevboost.service

• Set auto start of Mev boost service on system startup

  sudo systemctl enable mevboost

• Link Beacon service to Mevboost client

  sudo nano /etc/systemd/system/consensus-beacon.service

  NOTE: Replace consensus-beacon for your beacon service name

  Extend its ExecStart for following flag:

  --builder http://127.0.0.1:18550

  --validators-builder-registration-default-enabled=true \
  				--builder-endpoint=http://127.0.0.1:18550

  --builder \
  				--builder.urls http://127.0.0.1:18550

  --payload-builder=true \
  				--payload-builder-url=http://127.0.0.1:18550

  --http-mev-relay=http://127.0.0.1:18550

  Restart Daemon

  sudo systemctl daemon-reload

  Restart the Beacon service

  sudo systemctl restart consensus-beacon.service && systemctl status consensus-beacon.service

  Monitor the service

  journalctl -f -u consensus-beacon.service

  • Restart the Beacon service

    /usr/local/bin/staking.sh restart beacon && /usr/local/bin/staking.sh status beacon

  • Monitor the service

    /usr/local/bin/staking.sh monitor beacon

• Link each Validator service to Mevboost client

  sudo nano /etc/systemd/system/validator.service

  NOTE: Replace validator for your validator service name

  Extend its ExecStart for following flag:

  --builder-proposals

  --validators-builder-registration-default-enabled=true

  --builder

  --payload-builder=true

  --enable-builder

  Restart Daemon

  sudo systemctl daemon-reload

  Restart the validator service(s)

  sudo systemctl restart validator.service && systemctl status validator.service

  Monitor the validator service(s)

  journalctl -f -u validator.service

  • Restart validator service(s)

    /usr/local/bin/staking.sh restart validators && /usr/local/bin/staking.sh status validators

  • Monitor validator service(s)

    /usr/local/bin/staking.sh monitor validators