Make Checkpoint sync work for PeerDAS #6026
Labels
das
Data Availability Sampling
Comments
|
@michaelsproul what about changing the invariant to exclude the finalized block? |
mergify bot
pushed a commit
that referenced
this issue
Jan 31, 2025
Addresses #6026. Post-PeerDAS the DB expects to have data columns for the finalized block. Instead of forcing the user to submit the columns, this PR computes the columns from the blobs that we can already fetch from the checkpointz server or with the existing CLI options. Note 1: (EDIT) Pruning concern addressed Note 2: I have not tested this feature Note 3: @michaelsproul an alternative I recall is to not require the blobs / columns at this point and expect backfill to populate the finalized block
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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_columnsHTTP 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
The text was updated successfully, but these errors were encountered: