MEV Relay (For Validators)

Node operators should set up MEV-Boost to connect to bloXroute MEV relay.

Setup MEV-Boost

Please refer to mev-boost usage instructions and a full set of setup instructions in the testing guide on GitHub.

Mev-boost is available on Github or Docker Hub.

Relay Types

bloXroute operates two types of MEV relays—Max Profit and Regulated—which are available for both validators and builders to connect to. While historically distinct, both relays currently enforce the same filtering policy: they propagate all available transactions and bundles except those interacting with OFAC-sanctioned addresses. Despite having identical behavior today, bloXroute continues to maintain both relay names for backward compatibility and integration consistency.

Relay Endpoints

Validators running mev-boost can connect to bloXroute’s MEV relays on Ethereum Mainnet to receive full blocks proposed by bloXroute.

bloXroute offers two types of MEV relays:

• Max Profit Relay – prioritizes maximum validator rewards

• Regulated Relay – enforces the same OFAC filtering but was originally intended for stricter regulatory environments

Validators may choose either relay type and include it in the -relays startup argument of mev-boost.

Mainnet Relay Endpoints

• Max profit relay: https://0x8b5d2e73e2a3a55c6c87b8b6eb92e014[e-mail]

• Regulated relay: https://0xb0b07cd0abef743db4260b0ed50619cf[e-mail]

Example Usage (Mainnet Relay Endpoint):

./mev-boost \
  -mainnet \
  -relays \
https://0x8b5d2e73e2a3a55c6c87b8b6eb92e014[e-mail],\
https://0xb0b07cd0abef743db4260b0ed50619cf[e-mail]

Validators can append ?id= parameter to the end of relay URL. You may also append parameters such as ?id=your-validator-name and &auth=your-auth-token when using Relay-Proxy configurations. Example Usage (Mainnet Relay Endpoint w/ Validator ID):

./mev-boost -mainnet -relays https://0x8b5d2e73e2a3a55c6c87b8b6eb92e014[e-mail]?id=validator-name

** It is recommended that validators connect to multiple MEV relays to maximize block proposal opportunities and resilience. This includes connecting to the bloXroute relays, as well as other major relays such as Flashbots, Ultrasound, and others.

Skip Optimism

Validators can also append the ?skip_optimism=true parameter to the end of a bloXroute relay URL to enforce full simulation of all blocks before receiving a header. This ensures that only fully simulated blocks are considered during block proposal.

By default, bloXroute does not simulate blocks from trusted builders who have an established relationship with us—this allows for faster header delivery. However, setting skip_optimism=true overrides this behavior and ensures every block is simulated, regardless of the builder’s trust level.

Example Usage (Mainnet Relay Endpoint w/ Validator ID and Skip Optimism enabled):

./mev-boost -mainnet -relays https://0x8b5d2e73e2a3a55c6c87b8b6eb92e014[e-mail]?id=validator-name&skip_optimism=true

Testnet Validators

Validators using mev-boost can now connect to bloXroute’s MEV relays on both Holesky and Hoodi testnets to receive full blocks proposed by bloXroute.

Holesky Relay URL

• https://0x821f2a65afb70e7f2e820a925a9b4c80[e-mail]

Hoodi Relay URL

• https://0x821f2a65afb70e7f2e820a925a9b4c80[e-mail]

Example Usage (Testnet Relay Endpoint w/ Validator ID)

# Example Holesky args
./mev-boost -genesis-fork-version 0x01017000 -relays https://0x821f2a65afb70e7f2e820a925a9b4c80[e-mail]?id=<validator-name>

# Example Hoodi args
./mev-boost -genesis-fork-version 0x10000910 -relays https://0x821f2a65afb70e7f2e820a925a9b4c80[e-mail]?id=<validator-name>