MEV-Boost Relay for Ethereum proposer/builder separation (PBS).
Currently live at:
- https://boost-relay.flashbots.net (also on Goerli and Sepolia)
- https://relay.ultrasound.money
- https://agnostic-relay.net
- https://relay.edennetwork.io/info
- https://relayooor.wtf
- https://mainnet-relay.securerpc.com
- https://mainnet.aestus.live
The relay consists of several components that are designed to run and scale independently and to be as simple as possible:
- API: for proposer, block builder, data.
- Website: handles the root website requests (information is pulled from Redis and database).
- Housekeeper: update known validators, proposer duties.
Dependencies:
- Redis
- PostgreSQL
- one or more beacon nodes
- block submission validation nodes
A security assessment for the relay was conducted on 2022-08-22 by lotusbumi. Additional information can be found in the Security section of this repository.
See also:
MEV is a centralizing force on Ethereum. Unattended, the competition for MEV opportunities leads to consensus security instability and permissioned communication infrastructure between traders and block producers. This erodes neutrality, transparency, decentralization, and permissionlessness.
Flashbots is a research and development organization working on mitigating the negative externalities of MEV. Flashbots started as a builder specializing in MEV extraction in proof-of-work Ethereum to democratize access to MEV and make the most profitable blocks available to all miners. >90% of miners are outsourcing some of their block construction to Flashbots today.
The mev-boost relay is a trusted mediator between block producers and block builders. It enables all Ethereum proof-of-stake validators to offer their blockspace to not just Flashbots but other builders as well. This opens up the market to more builders and creates competition between them, leading to more revenue and choice for validators, and better censorship-resistance for Ethereum.
In the future, proposer/builder separation will be enshrined in the Ethereum protocol itself to further harden its trust model.
Read more in Why run mev-boost? and in the Frequently Asked Questions.
# Start PostgreSQL & Redis individually:
docker run -d -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres postgres
docker run -d -p 6379:6379 redis
# Or with docker-compose:
docker-compose upNote: docker-compose also runs an Adminer (a web frontend for Postgres) on http://localhost:8093/?username=postgres (db: postgres, username: postgres, password: postgres)
The services need access to a beacon node for event subscriptions. You can also specify multiple beacon nodes by providing a comma separated list of beacon node URIs.
The beacon API by default is using localhost:3500 (the Prysm default beacon-API port).
You can proxy the beacon-API port (eg. 3500 for Prysm) from a server like this:
ssh -L 3500:localhost:3500 your_serverNow start the services:
# The housekeeper sets up the validators, and does various housekeeping
go run . housekeeper --network sepolia --db postgres://postgres:postgres@localhost:5432/postgres?sslmode=disable
# Run APIs for sepolia (using a dummy BLS secret key)
go run . api --network sepolia --secret-key 0x607a11b45a7219cc61a3d9c5fd08c7eebd602a6a19a977f8d3771d5711a550f2 --db postgres://postgres:postgres@localhost:5432/postgres?sslmode=disable
# Run Website for sepolia
go run . website --network sepolia --db postgres://postgres:postgres@localhost:5432/postgres?sslmode=disable
# Query status
curl localhost:9062/eth/v1/builder/status
# Send test validator registrations
curl -X POST localhost:9062/eth/v1/builder/validators -d @testdata/valreg2.json
# Delete previous registrations
redis-cli DEL boost-relay/sepolia:validators-registration boost-relay/sepolia:validators-registration-timestampDB_TABLE_PREFIX- prefix to use for db tables (default usesdev)DB_DONT_APPLY_SCHEMA- disable applying DB schema on startup (useful for connecting data API to read-only replica)BLOCKSIM_MAX_CONCURRENT- maximum number of concurrent block-sim requests (0 for no maximum)FORCE_GET_HEADER_204- force 204 as getHeader responseDISABLE_BLOCK_PUBLISHING- disable publishing blocks to the beacon node at the end of getPayloadDISABLE_LOWPRIO_BUILDERS- reject block submissions by low-prio buildersDISABLE_BID_MEMORY_CACHE- disable bids to go through in-memory cache. forces to go through redis/dbNUM_ACTIVE_VALIDATOR_PROCESSORS- proposer API - number of goroutines to listen to the active validators channelNUM_VALIDATOR_REG_PROCESSORS- proposer API - number of goroutines to listen to the validator registration channelACTIVE_VALIDATOR_HOURS- number of hours to track active proposers in redis (default: 3)GETPAYLOAD_RETRY_TIMEOUT_MS- getPayload retry getting a payload if first try failed (default: 100)API_TIMEOUT_READ_MS- http read timeout in milliseconds (default: 1500)API_TIMEOUT_READHEADER_MS- http read header timeout in milliseconds (default: 600)API_TIMEOUT_WRITE_MS- http write timeout in milliseconds (default: 10000)API_TIMEOUT_IDLE_MS- http idle timeout in milliseconds (default: 3000)BLOCKSIM_TIMEOUT_MS- builder block submission validation request timeout (default: 3000)
- Edit the HTML in
services/website/website.html - Edit template values in
testdata/website-htmldata.json - Generate a static version of the website with
go run scripts/website-staticgen/main.go
This builds a local copy of the template and saves it in website-index.html
The website is using:
See ARCHITECTURE.md for more technical details!
Flashbots is a research and development collective working on mitigating the negative externalities of decentralized economies. We contribute with the larger free software community to illuminate the dark forest.
You are welcome here <3.
- If you have a question, feedback or a bug report for this project, please open a new Issue.
- If you would like to contribute with code, check the CONTRIBUTING file for further info about the development environment.
- We just ask you to be nice. Read our code of conduct.
If you find a security vulnerability on this project or any other initiative related to Flashbots, please let us know sending an email to security@flashbots.net.
The code in this project is free software under the AGPL License version 3 or later.
Made with ☀️ by the ⚡🤖 collective.