Weekly update on mev-boost development, implementation, testing, content and education.
Development updates
- mev-boost source code audit has started
- Sepolia testnet merge: preparing Flashbots Builder+Relay
- Released mev-boost v0.6.0: https://github.com/flashbots/mev-boost/releases/tag/v0.6.0
- First draft of the mev-boost Relay API specification - call for review
- Planning continues on the Relay Monitor
- Discussions in mev-boost:
- Support validator account level relay choice #154
- Allow loading a list of relays from an API #136
- Discussions in builder-specs:
- Extend PayloadAttributes with configurable gas_limit #29
- Consider running builder software through the Merge testing #32
- Clarify relationship b/t builder, relay and proposer #23
Testing and implementation
- Ongoing testing on Kiln and Ropsten
- At the Sepolia merge next week, several validators will run nodes connected to mev-boost
Consensus client implementation status of the builder-spec:
✅ Teku - working & tested. Guide
⏳ Lighthouse - testable integration in a feature branch. Guide
🐌 Lodestar, Nimbus & Prysm - still implementing, not yet testable
Content and education
- Research: MEV-Boost for Lido validators - interesting insights for anyone thinking about implementing mev-boost
- Lido survey: https://research.lido.fi/t/lido-on-ethereum-node-operator-mev-survey/2454
- New guide for testing mev-boost with Lighthouse
- Post by Jolene: https://writings.flashbots.net/writings/beginners-guide-mevboost
💡 Learn more about mev-boost at https://github.com/flashbots/mev-boost, and about Flashbots at docs.flashbots.net
⭐ You can help with documenting and testing by connecting to our relays on Kiln, Ropsten (and next week on Sepolia too). And by asking your favourite consensus client team to wrap up implementation of the builder spec!