2026-11-16 20:46 UTCf988af
How to Set Up MEV-Boost on a Validator for Builder Blocks
With your Ethereum validator already running, set up MEV-Boost by starting it with trusted mainnet relays, pointing your beacon node at its local…
Crypto Record Editorial3 min read

With your Ethereum validator already running, set up MEV-Boost by starting it with trusted mainnet relays, pointing your beacon node at its local endpoint, enabling builder proposals in the validator client, and confirming registration with each relay. The Flashbots Relay is one relay option; MEV-Boost, developed by Flashbots, runs beside the consensus client, forwards signed validator registrations to relays, and passes their highest valid bid back to the client. When no valid bid arrives, the consensus client falls back to building the block locally.
Mainnet Prerequisites and Relay Choice
Mainnet setup starts with synced execution and Beacon Chain clients, an active validator, the MEV-Boost binary, a fee recipient address, and relay URLs that include each relay’s public key. Set the fee recipient in the validator client: its signed registration carries that address to relays, so verify it before restarting.
Relay choice determines which builders can bid for your slots and which transaction policies you accept. Compare each relay’s censorship policy and reliability, including its history of timely responses. The Flashbots Relay is one option, but every relay in your configuration must be one you trust: a listed relay can supply a bid you may sign.
MEV-Boost Setup and Registration
MEV-Boost connects the relays to your beacon node, while the validator client authorizes builder proposals.
- Confirm the starting state. Make sure both clients are synced and the validator is active. Copy each mainnet relay URL in the form https://<RELAY_PUBKEY>@<RELAY_HOST>, and have your validator public key ready for the final check.
- Start MEV-Boost. Run mev-boost -mainnet -relay-check -relays <URL1,URL2> -min-bid <ETH>, replacing the comma-separated URLs and bid threshold with your choices. MEV-Boost listens on localhost:18550 by default. The -relay-check flag checks relay status at startup. Set -min-bid to the smallest builder payment you are willing to accept: when every bid falls below that amount, MEV-Boost returns no bid and the consensus client builds locally. A higher threshold means more slots can take that local path.
- Wire up the clients. Point the beacon node’s builder endpoint to localhost then enable builder proposals in the validator client. For Lighthouse, use --builder on the beacon node and --builder-proposals on the validator client. For Prysm, use --http-mev-relay and --enable-builder, respectively. Teku uses --builder-endpoint and --validators-builder-registration-default-enabled=true. Nimbus uses --payload-builder=true on both processes and --payload-builder-url on the beacon node.
- Restart the beacon node and validator client. Keep MEV-Boost running before they reconnect. The validator client signs registrations containing its fee recipient; the beacon node sends them through MEV-Boost to the configured relays.
- Confirm registration at every relay. Request /relay/v1/data/validator_registration?pubkey=<YOUR_VALIDATOR_PUBKEY> from each relay’s HTTPS host, using the host after the @ in its configured URL. Match the returned registration and fee recipient to your validator, then look for successful registerValidator calls for each relay in the MEV-Boost logs. Those checks confirm the validator is registered without waiting for a proposal.
Related Questions
Which MEV-Boost relays should I use?
Choose relays whose censorship policies you accept and whose response reliability suits your setup. Add only relays you trust; MEV-Boost can request bids from all of them through one local endpoint.
How to check if MEV-Boost is working?
Use each relay’s registration response and the corresponding successful registerValidator log entry as your setup check. Once both appear for every chosen relay, keep MEV-Boost running for your next proposal.