Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion developers/retrievability.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: Practices and expectations for data retrievability and pruning on C
# Data retrievability and pruning

The purpose of data availability layers such as Celestia is to ensure
that block data is provably published to the Internet, so that applications
that block data is provably published, so that applications
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@evan-forbes i think leaving in "to the Internet" makes it clearer, but curious what you think.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reviewed with Evan and good to go! thank you @howdymary

and rollups can know what the state of their chain is, and store that data.
Once the data is published, data availability layers
[do not inherently guarantee that historical data will be permanently stored](https://notes.ethereum.org/@vbuterin/proto_danksharding_faq#If-data-is-deleted-after-30-days-how-would-users-access-older-blobs)
Expand Down