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

Make Checkpoint sync work for PeerDAS #6026

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

Make Checkpoint sync work for PeerDAS #6026

jimmygchen opened this issue Jul 1, 2024 · 1 comment
Labels
das Data Availability Sampling

Comments

@jimmygchen
Copy link
Member

Description

Prior to PeerDAS, checkpoint sync requires downloading / providing the checkpoint blob. The rationale is documented here.

From PeerDAS, unless we make all checkpoint servers supernodes AND implement an new /data_columns HTTP endpoint for this, beacon nodes will have to fetch data columns for the checkpoint block via p2p instead of HTTP.

@michaelsproul and @dapplion suggested that we can either briefly allow the invariant to break briefly (storing block first, and then store data columns once they're downloaded) on startup or move the invariant target to the first block after anchor point.

Part of #4983

@jimmygchen jimmygchen added the das Data Availability Sampling label Jul 1, 2024
@jimmygchen jimmygchen mentioned this issue Jul 1, 2024
52 tasks
@dapplion
Copy link
Collaborator

dapplion commented Jul 1, 2024

@michaelsproul what about changing the invariant to exclude the finalized block?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
das Data Availability Sampling
Projects
None yet
Development

No branches or pull requests

2 participants