What is data availability (DA)?
- Author
- CRYPTO PORT Editorial
- Published
- Updated
- Reading time
- 6 min
In short
Data availability means the transaction data behind a block has actually been published and anyone can fetch it. Without that data, no third party can recompute the state or challenge a fraudulent claim. Where a rollup puts its data therefore shapes how safe it is.
Key points
- The condition that block data is published and fetchable by anyone
- Without it, no one can recompute state or challenge fraud
- Posting to layer 1 versus an external service changes the risk
- It asks whether data can be obtained, not whether it is correct
Definition
The property that the transaction data needed to reconstruct a block has genuinely been published and can be retrieved by third parties. It concerns obtainability, not correctness.
A rollup executes transactions off layer 1 and records only the outcome there. If the underlying transaction data is never published, users cannot recompute their own balances, and no one can disprove an operator that asserts a wrong state. Data availability is the precondition that makes verification possible at all.
Terminology follows where the data lives. A system that posts transaction data to layer 1 is a rollup; one that keeps it with an off-chain committee or a separate chain is called a validium or an optimium. The latter is cheaper, but if whoever holds the data refuses to release it, withdrawals can become impossible.
On Ethereum, the blobs introduced by EIP-4844 serve as the data area for rollups. Blobs are designed to be pruned by nodes after a set period, so they are not permanent storage. Anyone who needs the long-term history has to keep an archive of it separately.
Data availability sampling is a technique for confirming, with high probability, that an entire block was published without downloading all of it: a node repeatedly requests random fragments. Combined with erasure coding, it lets lightweight nodes take part in verification.
Watch out for
- · When data is entrusted to an external service, withdrawals can stall if that operator stops publishing it
- · Some systems marketed as rollups do not post data to layer 1 — check the documentation rather than the label
- · Blobs are pruned after a period, so old transaction data is not guaranteed to remain accessible