Add docs on data retrievability and pruning - #1123
Merged
Merged
Conversation
Contributor
|
liamsi
reviewed
Oct 9, 2023
liamsi
left a comment
liamsi
left a comment
Member
There was a problem hiding this comment.
I do think the params and suggested practices all make sense.
renaynay
approved these changes
Oct 10, 2023
Wondertan
reviewed
Oct 10, 2023
|
|
||
| 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. |
Contributor
There was a problem hiding this comment.
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.
musalbas
marked this pull request as ready for review
October 11, 2023 14:45
jcstein
self-requested a review
October 11, 2023 15:23
jcstein
requested changes
Oct 11, 2023
…ubmit-data" in sidebar" This reverts commit 5285e22.
jcstein
approved these changes
Oct 11, 2023
jcstein
reviewed
Oct 11, 2023
Co-authored-by: Josh Stein <46639943+jcstein@users.noreply.github.com>
Co-authored-by: Josh Stein <46639943+jcstein@users.noreply.github.com>
Co-authored-by: Josh Stein <46639943+jcstein@users.noreply.github.com>
Co-authored-by: Josh Stein <46639943+jcstein@users.noreply.github.com>
…org/docs into musalbas/retrievability
Co-authored-by: Josh Stein <46639943+jcstein@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.