Engine API specification for a new optionalgetBlobsV1 method.
The purpose of this method is to allow consensus clients to fetch blobs from the EL blob pool, so that:
It reduces the delay for a block to become available and attestable, if the blobs aren't received via gossip in a timely manner e.g. due to limited proposer bandwidth, or high latency at the receiving node.
Secondly it enables "decentralized blob building", which reduces the likelihood of a block getting orhpaned if the block proposer isn't able to publish the blobs quick enough due to bandwidth constraints (e.g. home stakers with limited bandwidth or stakers in remote locations). High capacity nodes can fetch blobs from their EL blob pools, build the blob sidecars and publish it to the network on behalf of the proposer. This will help self builders today (which statistically include a higher number of blobs in their blocks), and will become an important component to keep local block building viable for home stakers when blob count increases in the near future.
Engine API specification for a new optional
getBlobsV1method.The purpose of this method is to allow consensus clients to fetch blobs from the EL blob pool, so that:
Co-authored with @jimmygchen