📡 Data Availability Data Availability
The guarantee that the transaction data behind a block has actually been published, so anyone on the network can download it and check the block is valid for themselves. Often shortened to DA.
📋 The simple version — show your work
Think of a teacher who has to post the full answer key on a public board, not just the final grades. Anyone can spot-check a few answers at random, and if the teacher tried to hide the work, the gaps would be obvious. Data availability is that rule for a blockchain. A block producer must publish the underlying transaction data, not just a tidy summary. If they hide it, nobody can prove the block is honest.
🎲 How do you check without downloading everything?
Downloading every block in full is heavy. The trick is data availability sampling (DAS): a small "light" node grabs a handful of random pieces instead of the whole block. First the data is expanded with erasure coding, which adds redundancy so the data can be rebuilt even if some pieces go missing. Because of that math, if any of the original data is being hidden, about half of the expanded pieces would be missing — so a few random samples give you very high confidence the full data is really there.
| Step | What happens |
|---|---|
| 🧩 Erasure coding | The block's data is expanded with redundancy, so missing pieces can be reconstructed |
| 🎲 Random sampling | A light node downloads a few small random chunks instead of the whole block |
| 📈 Statistical confidence | If the samples are all present, it's overwhelmingly likely the full data is available |
🧱 Why beginners meet it: Layer 2 and rollups
Data availability is the backbone of Layer 2 scaling. A rollup runs transactions off the main chain to save fees, then posts the data back. That data must be available, or no one can check the rollup's work and it can't be trusted. It shows up two ways:
- ⚖️ Optimistic rollups — They assume transactions are honest unless challenged. A challenge (fraud proof) is only possible if the transaction data actually exists to inspect.
- 🔐 ZK-rollups — Even with a zero-knowledge proof that the math is correct, users still can't know their own balances if the operator withholds the data. So availability is still required.
📊 Posting this data is the biggest cost a rollup pays. Ethereum's EIP-4844 added cheaper temporary data space called "blobs" to make that posting cheaper for rollups.
🏗️ Dedicated DA layers
Instead of forcing the main Layer 1 to carry every byte, some projects build a separate layer whose only job is making data available. This is part of the modular blockchain idea — splitting one chain's jobs across specialized layers.
- 🟪 Celestia (TIA) — the first purpose-built modular data availability network; it pioneered sampling for light nodes
- 🔁 EigenLayer / EigenDA — data availability secured on Ethereum through restaking, rather than a separate chain
- 🟦 Avail — a DA layer (originally from Polygon) that combines erasure coding with a committee
🚨 Things beginners should know
- 🗄️ Availability ≠ storage — DA is about data being published now for verification, not about keeping it forever
- 📥 Not everyone downloads everything — sampling confirms the data is there without a full download
- 🚪 Where the data lives matters — posting to a cheaper DA layer cuts fees but can change the security and trust assumptions of a rollup
❓ FAQ
- Does data availability mean the data is stored forever?
- No. Availability is about whether the data was published right now, so blocks can be verified today. Keeping old data around for the long term is a separate idea, and it isn't needed to verify new blocks.
- Does every node have to download the whole block?
- No, and that's the clever part. With data availability sampling, a light node downloads a few small random pieces. Thanks to erasure coding, those few checks are enough to be confident the full data is there, without downloading all of it.
- Why do I keep seeing data availability next to Layer 2 and rollups?
- Rollups run transactions off-chain and then post the data back. If that data isn't available, no one can check the rollup's work, so the rollup can't be trusted. Posting this data is also the biggest cost a rollup pays.