Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement getBlobSidecars support for PeerDAS #6251

Open
Tracked by #4983
jimmygchen opened this issue Aug 12, 2024 · 1 comment
Open
Tracked by #4983

Implement getBlobSidecars support for PeerDAS #6251

jimmygchen opened this issue Aug 12, 2024 · 1 comment
Labels
das Data Availability Sampling HTTP-API

Comments

@jimmygchen
Copy link
Member

Description

The getBlobSidecars beacon API needs a bit of work to make it functional for PeerDAS, as full blobs will no longer be stored in every node, and will be stored in the form of data columns.

For supernodes and nodes with > 50% columns, this should be relatively straight forward, as the node would be able to reconstruct the blobs locally and serve them.

For regular full nodes, they would need to fetch at least 50% of columns, perform reconstruction before the blobs can be served.

@jimmygchen jimmygchen added the das Data Availability Sampling label Aug 12, 2024
@jimmygchen
Copy link
Member Author

jimmygchen commented Aug 20, 2024

A few other clients have implemented this, and only serve the request if the node already have at least 50% of columns.

Fetching 50% / 64 columns from peers isn't necessary expensive - it's equivalent to performing 4 slots of peer sampling, which we do a lot more than this during head sync. However, this would allow HTTP APIs to requests the p2p network, which we want to avoid.

Probably best to implement this endpoint for nodes custodying >= 50% of columns for now.

@jimmygchen jimmygchen mentioned this issue Aug 21, 2024
52 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
das Data Availability Sampling HTTP-API
Projects
None yet
Development

No branches or pull requests

1 participant