Data Availability
Pronunciation: DAY-tuh uh-vay-luh-BIL-uh-tee
Definition
Data availability is the property that the data needed to verify, reconstruct, or continue a blockchain state transition can be obtained by network participants. A valid block or proof may show that rules were followed without ensuring users can retrieve the underlying transaction or state data.
Overview
Meaning and scope
Data availability is the property that the data needed to verify, reconstruct, or continue a blockchain state transition can be obtained by network participants. A valid block or proof may show that rules were followed without ensuring users can retrieve the underlying transaction or state data.
Mechanism and operation
Blockchain verification requires more than a commitment to data. Base-layer blockchains often require validators to download block data before voting. Modular and rollup designs can publish data to another layer, use erasure coding and sampling, or rely on external committees. Each approach changes who can verify availability and what assumptions remain. Data availability sampling lets nodes request small random portions of erasure-coded data and gain probabilistic confidence that the full data set can be recovered. The security depends on sampling parameters, encoding, peer distribution, and the number of honest participants. For rollups, proof validity does not replace data availability.
Practical payment example
A rollup publishes a validity proof but withholds transaction data. Users cannot independently reconstruct accounts or exits, even though the proof verifies the claimed computation.
Operational checks
A valid state transition can still leave users unable to reconstruct balances or submit exits if transaction data is withheld. Payment and bridge systems should track publication and availability separately from sequencer acceptance and proof verification. Protocol data may be available for a required window but later pruned from ordinary nodes.
Distinctions and limits
Participants need access to the underlying transactions, blobs, or state-difference information required to reproduce the state, generate proofs, or exit a dependent system. Applications needing historical reconciliation should maintain archives or use providers with documented retention and integrity guarantees. Data Availability should be assessed at the level of its deployed verifier and parameters, not from the proof-system label alone.
Related reading
Related definitions: rollup, Data availability sampling.
Example
A rollup publishes a validity proof but withholds transaction data. Users cannot independently reconstruct accounts or exits, even though the proof verifies the claimed computation.
Comparison
Participants need access to the underlying transactions, blobs, or state-difference information required to reproduce the state, generate proofs, or exit a dependent system. The security depends on sampling parameters, encoding, peer distribution, and the number of honest participants.
Key Takeaway
Data availability ensures participants can obtain the data behind state transitions; it is distinct from proof validity, execution success, finality, and archival retention.
Sources
- EIP-4844: Shard Blob Transactions — Ethereum Foundation (2026-08-01)