Skip to content

Data Availability

What data availability means for rollups: the guarantee that transaction data can be retrieved and verified, why it differs from data storage, and how it decides what a rollup can honestly claim.

Data availability is the guarantee that the underlying data behind a transaction or a rollup batch is actually retrievable by anyone who wants to check it — not merely that a compressed commitment or hash of that data exists somewhere on-chain. A hash proves data existed; availability means the data itself can still be pulled down and verified.

This distinction matters because a rollup’s whole security model depends on outside parties being able to reconstruct the L2’s state from what’s published on L1. If the underlying data is withheld or lost, nobody can independently check whether a rollup’s state transitions were honest, even if a validity proof or fraud proof mechanism exists in theory.

Why it matters

Where a rollup gets its data availability from is one of the clearest ways to compare L2 designs. Rollups that post full transaction data to Ethereum via blobs inherit Ethereum’s security for that data. Rollups that instead rely on a separate, external data-availability layer or committee are making a different, generally weaker, trust tradeoff in exchange for lower costs — worth knowing before treating two L2s as interchangeable.

Example

If a sequencer published only a state root with no accompanying transaction data, nobody outside the sequencer could reconstruct how that state was reached or dispute it — which is exactly the failure mode data-availability guarantees are designed to rule out.

Related · Rollups

← All glossary terms

Not financial advice.