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.

2. Write a basic specification that is conservative, centralized, and trusted.

✔️ Specification v0.2

3. Move the API to Ethereum specs, polish and make it ready to be implemented.

✔️ https://github.com/ethereum/builder-specs

4. Implement the specification in mev-boost and mergemock.

[Milestone: merge-ready. Expected deadline, second week of may]

✔️ https://github.com/protolambda/mergemock/pull/26

⏳ https://github.com/flashbots/mev-boost/pull/119

5. Implement the specification in the flashbots builder.

[Milestone: merge-ready. Expected deadline, second week of may]

5. Implement the specification in the consensus clients.

[Milestone: end-to-end-ready. Expected deadline, end of may for the first client]

[Milestone: all-client-support. Expected deadline, mid june]

6. Test with kiln, hive, kurtosis.

[Milestone: end-to-end-ready. Expected deadline, end of may]

7. Add requirements specific for validator pools.

[Milestone: validator-pool-extras. Expected deadline, mid june]

8. Add requirements specific for big validators.

[Milestone: big-extras. Expected deadline, end of june]

9. Add a second independent builder. [Expected deadline, end of june]

10. Explore the options for decentralization of the builders. [Expected deadline, august]

11. Explore the options for decentralization of the orderflow. [Expected deadline, august]

12. [...]

13. Magic. [daily during sunset 🌞]

14. In protocol PBS. [Expected deadline, 2023]