search

celestiaorg / celestia-core

A fork of CometBFT
Apache License 2.0
486 stars 263 forks source link

"Delete" data in non-reserved namespaces after X days (where X is some network-wide parameter that is TBD) #1235

Open musalbas opened 1 year ago

musalbas commented 1 year ago

See e.g. https://notes.ethereum.org/@vbuterin/proto_danksharding_faq#If-data-is-deleted-after-30-days-how-would-users-access-older-blobs

This means that in the block validity rule, we would not verify data availability of non-reserved namespaces blocks older than X days, instead we rely on a weak subjectivity assumption if syncing from scratch. Data in reserved namespaces would still be verified as that pertains to the Celestia chain itself.

This might not be critical for mainnet itself, but may become more necessary as the chain's size increases.

musalbas commented 1 year ago

If we want "full nodes" to be able to sync from genesis by recomputing the data root from only reserved namespaced data -- I think this would require the full nodes to receive namespace proofs for the reserved namespaces, given they don't have the non-reserved data.

If they want to verify the PFB commitments are in the data root, this would require a blob inclusion proof for each PFB, but I'm not sure that's necessary under a weak subjectivity assumption -- or if it adds any extra security, if we don't require the data to be retrievable in the first place.