-
Notifications
You must be signed in to change notification settings - Fork 380
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
Add docs on data retrievability and pruning #1123
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do think the params and suggested practices all make sense.
docs/developers/retrievability.md
Outdated
|
||
Rollups may need to access historic data in order to allow new rollup nodes to reconstruct the latest state by replaying historic blocks. Once data has been published on Celestia and guaranteed to have been made available, rollups and applications are responsible for storing their historical data. | ||
|
||
While it is possible to continue do this by using the `GetAll` API method in celestia-node on historic blocks as long as archival nodes exist on the public Celestia network, rollup developers should not rely on this as the only method to access historical data, as archival nodes serving requests for historical data for free is not guaranteed. Below are some other suggested methods to access historical data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One idea, i’ve been discussing with Mary is the ability to plug various data sources into the node. In the same way, we have multiple options to get data from p2p, we can also allow developers to plug in CDNs, cloud providers, and web3 storage providers. This is similar to marketed Espresso’s tiramisu with the difference that we have required foundation implemented. If we enable plugging various standardized Getters, then there will be less need for Rollup devs to migrate off GetAll and implement custom interfaces and data retrievals. They would be able to just use standardized data sources in our ecosystem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
…ubmit-data" in sidebar" This reverts commit 5285e22.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - left some suggestions
Co-authored-by: Josh Stein <[email protected]>
Co-authored-by: Josh Stein <[email protected]>
Co-authored-by: Josh Stein <[email protected]>
Co-authored-by: Josh Stein <[email protected]>
…org/docs into musalbas/retrievability
Co-authored-by: Josh Stein <[email protected]>
No description provided.