Data Availability

What is Data Availability?

Data availability (DA) refers to the guarantee that transaction data has been published and can be retrieved by anyone who needs it. In the context of rollups, data availability ensures that the information required to reconstruct the rollup state and verify correctness is accessible, even if the sequencer goes offline or acts maliciously.

Without data availability, rollup security breaks down. Users could not verify state transitions, fraud proofs could not be generated, and the system would require trusting the sequencer completely. Data availability is therefore a foundational security requirement for all rollup designs.

How it Works

Data availability is achieved through several mechanisms:

• Transaction data posted directly to Ethereum calldata
• Stored by all Ethereum nodes forever
• Most secure but expensive (~16 gas per byte)
• Used by rollups before EIP-4844

• Transaction data posted as blobs via EIP-4844
• Stored for ~18 days, then pruned
• Much cheaper than calldata (~1 gas per byte equivalent)
• Current preferred method for Ethereum rollups

• Data stored with a Data Availability Committee
• Committee members attest to data availability
• Cheaper but introduces trust assumptions
• Used by validiums and some app-specific chains

• Celestia: Purpose-built DA layer with data availability sampling
• EigenDA: DA using Ethereum restaked security
• Avail: Polygon's modular DA solution

Practical Example

When Arbitrum processes a batch of transactions, it must make the underlying data available. Previously, this meant posting compressed calldata to Ethereum at significant cost. After EIP-4844, Arbitrum can post data as blobs, reducing costs by ~10x. Any full node can retrieve this blob data to verify the batch, generate fraud proofs if needed, or reconstruct the complete Arbitrum state. This data availability guarantee means users don't need to trust Arbitrum's sequencer. They can always verify independently.

Why it Matters

Data availability is crucial for several reasons:

• Security Foundation: Enables fraud proofs and state verification
• Censorship Resistance: Users can always force transactions through L1
• Trustless Operation: No reliance on sequencer honesty for fund safety
• State Reconstruction: Anyone can rebuild the rollup from DA

The cost of data availability is the primary driver of L2 transaction fees. EIP-4844 and future danksharding upgrades aim to dramatically reduce these costs while maintaining security guarantees.