Data Availability Sampling (DAS)

Overview

Data Availability Sampling reduces the burden of checking large block or blob data. Instead of downloading everything, many nodes request randomly selected pieces and verify them against a cryptographic commitment. Erasure coding adds redundancy so withholding any unrecoverable portion requires a large fraction of encoded pieces to be unavailable. Repeated random sampling then makes concealment increasingly likely to be detected, providing a probabilistic availability guarantee while preserving lightweight participation.

Implementations must verify commitments, sampling randomness, peer responses, coding parameters, and enough independent samples. DAS establishes that data was available, not that transactions were valid or executed correctly. Rollups and light clients still need the appropriate validity, fraud, or consensus verification for state transitions.

A rollup or shard can continue producing commitments while users remain unable to reconstruct the information required for independent verification. Applications relying on Data Availability Sampling (DAS) should identify how missing data is detected, how long data is retained, and what recovery path exists when normal providers fail. Operational monitoring should track publication delay, sampling success, reconstruction failures, provider diversity, and the relationship between availability evidence and canonical settlement. Capacity claims should be based on deployed parameters rather than projected roadmap throughput.

Data Availability Sampling (DAS) should be analyzed by separating data publication, commitment, sampling or retrieval, reconstruction, and final settlement. When evaluating Data Availability Sampling (DAS), a commitment can authenticate data without ensuring that users or validators can obtain enough of it to verify state or produce an exit. For example, a lightweight rollup verifier can sample coded data shares to detect withholding without downloading the entire published dataset.