The Plan (tm)

1. Define the architecture of the communication between consensus client, execution client, and mev-boost. :heavy_check_mark: 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. :heavy_check_mark: Specification v0.2
3. Implement the v0.2 specification in mev-boost, merge-mock, and the consensus clients. [Expected deadline, first week of may]
4. Implement the Flashbots builder. [Expeccted deadline, first wee of may]
5. Test the v0.2 specification with kiln, hive, kurtosis. [Expected deadline, second week of may]
6. Tag this version as Merge-Ready (tm).
7. Add a second independent builder.
8. Explore the options for full decentralization of the builders.
9. Explore the options for full decentralization of the orderflow.
10. [...]
11. Magic.
12. In protocol PBS.