Try   HackMD

Builder Updates for Blobs (EIP-4844)

Builder API is an interface that enables validators to delegate block building duties. The set of endpoints are exposed by an external block builder (e.g. mev-boost), and consumed by CL clients when proposing a block. EIP-4844 introduces additional changes to beacon block body, execution payload and "blob" data, hence changes will be required on both the Beacon API & builder API to support this.

Block Proposal - Builder flow

End-to-end block proposer flow

Image Not Showing Possible Reasons
  • The image was uploaded to a note which you don't have access to
  • The note which the image was originally uploaded to has been deleted
Learn More →

Beacon API & Builder API changes

mev_boostconsensusvalidatormev_boostconsensusvalidatoradd `blinded_blobs_bundle` to response (`SignedBuilderBid`)add `blinded_block_sidecars` to responseinclude `blob_kzg_commitments` in block and sign the headersign each `blinded_blob_sidecar` individuallysends `SignedBlindedBlockContents` (contains `signed_blinded_blobs`)returns revealed payload and full blobsconstruct block and broadcast block and blobsGET v2/validator/blinded_blocks/{slot}GET v1/builder/header/{slot}/{parent_hash}/{pubkey}GET v1/builder/header/{slot}/{parent_hash}/{pubkey} responseGET v2/validator/blinded_blocks/{slot} responsePOST beacon/blinded_blocksPOST /eth/v2/builder/blinded_blocksPOST /eth/v2/builder/blinded_blocks responseBlock Proposal with Builder API (EIP-4844)