MEV Relay Instructions for Ethereum Validators
Connect to Blocknative’s MEV-boost relay and monitoring APIs. Blocknative’s Ethereum relay is currently in alpha but has been heavily stress-tested.

Node operators need to set up MEV-Boost to connect to the Blocknative MEV relay. MEV-boost is available on Github or Docker Hub. Please refer to MEV-boost usage instructions and a full set of setup instructions in the testing guide on GitHub, outlined below. Our relay is also compliant with other MEV-boost compliant validators such as vouch.

MEV-boost can run in any machine, as long as it is reachable by the beacon client. The default port is 18550. The most common setup is to install it in the same machine as the beacon client.

Install MEV-boost with go install:
go install github.com/flashbots/[email protected]
mev-boost -help
Or clone the repository and build it:
git clone https://github.com/flashbots/mev-boost.git
cd mev-boost
make build
./mev-boost -help

An MEV-boost Docker image is maintained at https://hub.docker.com/r/flashbots/mev-boost
# Get the default mev-boost image
docker pull flashbots/mev-boost:latest
# Get the portable mev-boost image
docker pull flashbots/mev-boost:latest-portable
# Run it
docker run flashbots/mev-boost -help

If MEV-boost crashes with "SIGILL: illegal instruction" then you need to use a portable build:
You can either use a portable Docker image, or install/build the portable build like this:
# using `go install`
CGO_CFLAGS="-O -D__BLST_PORTABLE__" go install github.com/flashbots/[email protected]
# build from source
make build-portable

A single MEV-boost instance can be used by multiple beacon nodes. Note that aside from running MEV-boost, you will need to configure your beacon node to connect to MEV-boost and your validator to allow it to register with the relay. This configuration varies and a guide for each consensus client can be found on the MEV-boost website.

Blocknative provides one MEV relay that validators can connect to. The relay is:
  • publicly available
  • publicly listed & maintained
  • transparent about address filtering

Blocknative’s relay is currently in alpha but has been heavily stress-tested. It supports all Proposer and Builder APIs outlined in the Relay spec seen here. Currently, our relay has only one trusted builder, but we plan to expand to multiple external builders in the near future.
Validators with MEV-boost can connect to the Blocknative MEV relay in order to receive full blocks proposed by Blocknative. Validators can use the endpoints below:

https://0x9000009807ed12c1f08bf4e81c6da3ba8[email protected]builder-relay-mainnet.blocknative.com

https://0x8f7b17a74569b7a57e9bdafd2e1593807[email protected]builder-relay-goerli.blocknative.com

http://0xaef7ec27ca8ca24205aab89f6595a5ad6[email protected]builder-relay-ropsten.blocknative.com

To increase visibility and transparency Blocknative’s relay supports the following monitoring APIs. For a full list of API specs please visit Flashbot’s Relay API Spec.

get
<relayEndpointDomain>
/relay/v1/data/bidtraces/proposer_payload_delivered
BidTrace payloads delivered to proposers.
How to query:
curl -X GET builder-relay-ropsten.blocknative.com/relay/v1/data/bidtraces/proposer_payload_delivered

get
<relayEndpointDomain>
/relay/v1/data/bidtraces/builder_blocks_received
BidTrace payloads for blocks submitted by builders.
How to query:
curl -X GET builder-relay-ropsten.blocknative.com/relay/v1/data/bidtraces/builder_blocks_received

get
<relayEndpointDomain>
/relay/v1/data/validator_registration?pubkey=_pubkey_
Return the latest validator registration for a given pubkey.
Example query:
https://builder-relay-mainnet.blocknative.com/relay/v1/data/validator_registration?pubkey=0xa0f2dd347cf027be891a90d0661db3f095ebc013dc39261a7b206ef0685ab5666e7fe5b03673c02118f8807e8053c52e

If you have any questions about the Validator relay, join our discord.
Copy link
On this page
Setup MEV-boost
Installing
Dependencies
From source
From Docker image
Troubleshooting
Usage
Relay types
Relay Endpoints
Mainnet Validator
Goerli Validator
Ropsten Validator
Monitoring APIs
get
BidTrace payloads delivered to proposers.
get
BidTrace payloads for blocks submitted by builders.
get
Return the latest validator registration for a given pubkey.
Questions