-
Notifications
You must be signed in to change notification settings - Fork 211
The Plan (tm)
1. Define the architecture of the communication between consensus client, execution client, and mev-boost.
✔️ mev-boost will be a sidecar. The consensus client opts-in to use mev-boost. If it fails for any reason, the consensus client falls back to direct communication to the execution client.
✔️ Specification v0.2
✔️ https://github.com/ethereum/builder-specs
[Milestone: merge-ready.]
✔️ https://github.com/flashbots/mev-boost
✔️ https://github.com/protolambda/mergemock
✔️ https://builder-relay-ropsten.flashbots.net/ + https://builder-relay-kiln.flashbots.net/
[Milestone: merge-ready.]
✔️ https://github.com/flashbots/mev-boost/pull/223
[Milestone: merge-ready.]
✔️ Flashbots builder on Kiln and Ropsten is up and running.
[Milestone: end-to-end-ready. Expected deadline, end of june]
⏳ in progress, currently live testing
See also the consensus client implementation status table here: https://github.com/flashbots/mev-boost/wiki#implementation-status
[Milestone: all-client-support. Expected deadline, end of june]
[Milestone: validator-pool-extras. Expected deadline, mid july]
[Milestone: big-extras. Expected deadline, end of july]
https://github.com/flashbots/mev-boost/issues/224
[Milestone: safer-merge. Expected deadline, september]
[Milestone: safer-merge. Expected deadline, september]
[Milestone: safer-merge. Expected deadline, september]