Builder API Tracking

[realbigsean]

Description

This issue is meant to track outstanding work related to the Lighthouse implementation of the builder spec.

The goal is to make the https://github.com/sigp/lighthouse/tree/builder-api branch available for users, and for outstanding work here will be marked complete as it is merged into that branch. #3134 will remain open because it's already in use by some users and I'll do my best to keep it up to date with the builder-api branch.

• MEV boost JWT Auth not actually necessary, see the linked issue for discussion JWT Auth flashbots/mev-boost#52
• pre-Bellatrix block support on blinded endpoints [Merged by Bors] - Builder Specs v0.2.0 #3134
• support the normal proposal flow using the blinded blocks endpoints [Merged by Bors] - Builder Specs v0.2.0 #3134
• Add a local testnet setup to CI for the blinded block proposal flow without mev-boost
• Add a local testnet setup to CI for the blinded block proposal flow with mev-boost The purpose of this would have been to test lighthouse <> mev-boost compatibility, but because the mock_builder includes the mev-rs implementation of the builder API I don't actually think this adds much. Feels like we would end up testing mev-boost moreso than lighthouse
• Separate the engine api from the builder api because mev-boost no longer forwards engine - work started here [Merged by Bors] - Remove builder redundancy #3294

Issues

• [builder API] Make gas limit configurable #3295
• [builder API] Enable Web3Signer tests for validator registration #3296
• [builder API] Verify signatures on bids  #3297
• [builder API] Update to v0.2.0 #3298
• [builder API] Increase/add Timeouts #3319
• [builder API] Add --builder-timestamp-override #3337
• [builder API] Beacon chain health checks #3355
• [builder API] Enable builder API usage on a per-validator basis #3357

[realbigsean]

Completed in #3134