You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the existing endpoint, in the case where an L2 is able to compute the required slot from on-chain data, L2 server and CL client would both benefit from the ability to limit retrieval and transmission to only the necessary set of indices, which L2 knows by their versioned hashes. We could add another optional parameter versioned_hashes which would filter the response to a subset of blobs, just like the existing indices param: https://github.com/ethereum/beacon-APIs/blob/master/apis/beacon/blob_sidecars/blob_sidecars.yaml#L17-L25
Additional context
No response
The text was updated successfully, but these errors were encountered:
Problem description
Currently
getBlobSidecars
supports blockId and indices, but supporting versioned_hashes (optional) would help L2s relieve a pain point of mapping.Solution description
As identified here ,
Additional context
No response
The text was updated successfully, but these errors were encountered: