MEV-Boost is an implementation of proposer-builder separation (PBS) built by Flashbots for proof of stake Ethereum. Validators running MEV-Boost maximize their staking reward by selling blockspace to an open market of builders.
MEV-Boost is free, open-source, neutral software built with love, for the community. For information on MEV-Boost software and roadmap, see the MEV-Boost Repository.
- Install the latest version of MEV-Boost
- Connect MEV-Boost to desired MEV-Boost relays:
- Remember to use the appropriate network flag for the specific network and relay URL,
- Configure a consensus client. Detailed instructions are available on the MEV-boost testing wiki, and guides for connecting the client to mev-boost can be found in the consensus client compatibility table below.
- Confirm that the setup works by calling the data API to see your validator registration.
./mev-boost -mainnet -relay-check -relays relay1,relay2
For a comprehensive list of relay URL endpoints by network and operator maintained by the community, please refer to:
Flashbots Relay URLs
Consensus Client Compatibility 👫
MEV-Boost is designed to be compatible with the standard Ethereum Builder API. This means it is compatible with all consensus and execution clients. You can find guides for installing with your favorite consensus client below!
MEV-Boost Updates 🎯
We are writing regular updates about MEV-Boost development, adoption and community, for anyone interested in keeping up with our progress:
External builders can submit blocks to the Flashbots Relays on Mainnet, Goerli and Sepolia networks.
See here for more details:
- Flashbots Block Builders Official Documentation
- Relay API documentation - Block Builder API
- The Block Builder Self-Help Group forum
- Boost-geth-builder - example builder implementation built by Flashbots
MEV is Maximal Extractable Value. It is the profit a block proposer (miner or validator) can make through their ability to arbitrarily include, exclude, or re-order transactions from the blocks they propose.
mev-boost been audited?
Yes. The initial Audit Report for mev-boost can be found here:
mev-boost is designed to be used by any validator, no matter the size of its stake.
In Ethereum proof-of-work we had no way to prevent small miners from misbehaving and stealing MEV. Once identified, they could just get a new identity and continue misbehaving. The solution was to make a list of allowed miners that were big enough to be concerned about their reputation. Their profit would be severely affected if they were removed from the allowed list. This resulted in one more incentive for the concentration of mining power in a few organizations.
The most significant change for MEV in Ethereum proof-of-stake is that with
mev-boost now validators can be permissionless. The order is reversed: instead of the Flashbots relay sending blocks or bundles of transactions to the miners, now the validators request blocks to the Flashbots relay through
mev-boost. The Flashbots relay in turn requests blocks to a network of builders and gives the header of the most profitable one to the validator, while holding the payload in escrow. Once the validator signs the header, the relay sends the block payload to the proposer. If at this moment the validator decides to propose a different block, they will have signed two blocks and will be slashed.
Note that this does not mean that the system is fully permissionless and decentralized, yet. The Flashbots relay is still trusted.
Read the open research questions and join us exploring possible solutions.
Block building is a new role introduced by proposer-builder separation (PBS). Using MEV-Boost, validators can sell blockspace to specialized third parties called block builders who collect and sequence transactions to produce a block. Block builders want to produce a block that maximizes the fees collected in the form of priority fees and MEV.
Block builders must connect to a MEV-Boost relay in order to submit their payloads to validators for inclusion. Each relay may have different rules and provide access to different validators.
While we expect there will be several relays at the merge, block builders must be careful who they submit their payloads to. A relay has the power to censor or frontrun any block proposed by a block builder.
The Flashbots Relay (relay.flashbots.net) will start accepting block proposals from any block builder and continue our policy of neutrality and transparency. Documentation on the Flashbots Relay will be released closer to the merge.
Our relay will publish the logs of when blocks were received by builders and when they were supplied to proposers.
We expect several relay monitoring dashboards to emerge which keep track of relay performance and help block builders and validators to select a relay.
Slot collisions occur when more that one relay delivers a payload for a given slot. Multiple builders build blocks for a given slot, and these blocks can be submitted to multiple relays. If a block is the most profitable block for multiple relays at a given slot, it is possible each of these relays would return the block during a getHeader request for the same slot.
High/low builder prioritization works the same way it does for Flashbots searchers, which is to say that low/high priority get different simulation clusters and in times of high load, such that high-priority builders will be prioritized over low-priority builders. Reputation is just a mechanism to help mitigate DDOS attacks, but doesn't affect how Flashbots scores blocks.
- MEV-Boost documentation is live on docs.flashbots.net.
- For a deep dive on PBS, see The Hitchhiker's Guide to Ethereum.
- To understand the benefits and risks of running MEV-Boost, see Why run MEV-Boost?.
- If you are looking for an awesome guide on setting up mev-boost, see this post.
- For additional installation support, we recommend EthStaker Guide for Installing MEV-Boost.
- https://www.mevboost.org - overview of relays and builders which produced recent blocks
- https://mevboost.pics - charts and dashboards about the mev-boost and builder ecosystem
- https://boost-relay.flashbots.net - Flashbots mainnet mev-boost relay
* Users of this informational material are responsible for determining any applicable legal restrictions on any direct or derivative use of this information, including complying with applicable economic sanctions laws within their home jurisdictions. Please also see Github’s Trade Controls page. Flashbots makes no representation or warranty as to any Relay Operator or other entity’s compliance with economic sanctions or other laws and regulations.