Quick summary of what’s currently happening in and around MEV-Boost, as of Nov. 3, 2022.
Upcoming release of mev-boost v1.4.0
- Notably includes the ability to set a minimum bid value, under which mev-boost won’t provide a bid to the beacon node.
- Several minor improvements.
- More details at Upcoming mev-boost release: v1.4.0 · Issue #377 · flashbots/mev-boost · GitHub
- EIP 4844 will require changed to the builder-specs, mev-boost and the relays.
- See also Changes for Capella and EIP-4844 · Issue #392 · flashbots/mev-boost · GitHub
- An API that’s both useful to get verify active validators, and at the same time preserving proposer privacy
- Privacy Concerns with Data API
Current options that are discussed:
- Payment transaction at the end of the block
- Proposer balance different before/after the block
Main considerations include:
- Representation of “additional value provided to the proposer over a local EL block”
- Ability for adding payment proofs to the bid, which reflect that score and can be verified by mev-boost
Ongoing research on about adding inclusion lists, both outside and inside mev-boost.
There’s several open questions, including authorization of setting an inclusion list for a proposer/slot, timing of sending the IL, and ability to verify successful inclusion and valid exclusion reasons inside mev-boost.
Currently, the beacon node communicates with the builder network exclusively with JSON payloads. SSZ encoded payloads would increase encoding and decoding performance significantly, and reliably shave off hundreds of milliseconds off the request roundtrips.
- Allow SSZ encoding in addition to JSON encoding (for request and response payloads) · Issue #53 · ethereum/builder-specs · GitHub
- Provide first-class support for SSZ · Issue #250 · ethereum/beacon-APIs · GitHub
Currently, block builders depend on a custom Prysm fork to trigger block production as soon as all parameters are available.
This could also be a simple SSE subscription on the beacon node.
Eight relays have been delivering payloads in the last 24 hours:
(Source: Data API on the relays)
Note: multiple relays can deliver the same payload for a given slot (i.e. when a builder sends a winning bid to multiple relays).
At the time of writing, 83.3% of validators are running mev-boost connected to the Flashbots mainnet relay (382,719 out of 459,190). Here’s a chart of active validators over the past four weeks:
The Flashbots relay receives 300 bids from 30 builders for any given slot on average. These are builders who submitted more than 100 winning payloads (landed on chain) in the last 7 days: