Data Availability Layer
A data availability layer (DA layer) is a specialized blockchain or network component whose sole purpose is to guarantee that the raw data underlying a set of transactions has been published and can be downloaded by any network participant, without executing those transactions or maintaining the resulting state.
For a rollup or appchain to be trustworthy, users must be able to verify its correctness — and to do so, they need access to the underlying transaction data. If transaction data is withheld by a sequencer or block producer, even a perfectly valid-looking state root could have been produced fraudulently, and external parties would have no way to detect the fraud. Data availability is therefore not merely a storage problem but a cryptographic security requirement.
In a monolithic blockchain, data availability is bundled with execution and consensus: every full node downloads every block and verifies both the data and the computation. In a modular architecture, the DA layer separates this concern. It publishes ordered transaction data to a network of nodes, provides cryptographic proofs (typically using erasure coding and KZG or Reed-Solomon commitments) that the data was made available in full, and allows anyone to download and inspect it — without performing any execution itself.
Ethereum serves as a DA layer for rollups that post their calldata or blobs to it. After EIP-4844, rollups can post data in blob-carrying transactions that are stored temporarily (approximately two weeks) and are not processed by the Ethereum Virtual Machine, making posting to Ethereum dramatically cheaper.
Celestia, launched in mainnet in 2023, is a purpose-built DA layer that decouples availability entirely from execution. It uses a two-dimensional erasure coding scheme combined with data availability sampling (DAS), whereby light clients can verify with high probability that full data was published by downloading only a small random subset of each block, making it possible to run a DA-verifying light node with minimal hardware requirements.
EigenDA (built on EigenLayer), Avail, and Near DA are other competing DA layer solutions. Each makes different tradeoffs across cost, throughput, decentralization, and security model. For rollup developers choosing a DA layer, the primary considerations are cost per byte posted, finality latency, bridging and security assumptions back to the settlement layer, and the maturity of tooling.