This is a list of all the pieces I've written about Celestia and its related topics. If there's anything in particular you'd like to see explored, reach out to me on twitter. The different types of rollups that are possible with Celestia Secure light nodes and the scalability trilemma settlement layers in the modular stack A brief data availability and retrievability FAQ The state growth problem in a modular blockchain ecosystem A glimpse at the multi chain future

This is a non-exhaustive list of questions that have come up in Eric Wall's discussions regarding data availability. What is data availability? Data availability refers to the availability of transactions in a block that is appended to the tip of the chain. During consensus, validators download the block to verify its availability. If the block contains any transactions that are withheld by a validator, the block is unavailable and will be rejected as invalid. What is the difference between data availability and what we call data retrievability? Data availability is only concerned about the availability of a block when it is being proposed by a validator. Once the block has completed the consensus processes, is appended to the tip of the chain, and has propagated throughout the network, then the ability to download transactions from that block is what we call retrievability. This distinction is important because retrievability is a different problem from availability. What is the data availability problem? The data availability problem is concerned with the ability for nodes to verify that a block is available. For validators this occurs during consensus. For non-consensus nodes, this occurs when the block has passed consensus and is propagated throughout the network.