What blobs carry
Ethereum blobs give rollups a data space separate from execution data and use a distinct fee market. They can reduce data costs, but blobs are not ordinary contract-readable execution data and total transaction fees do not always fall when blob prices do.
How blobs differ from calldata
EIP-4844 describes blob transaction formats and validation, while Ethereum documentation distinguishes data availability from long-term retrievability. Check whether a rollup posts blobs or calldata, its batch cadence, and batch size. Implementations and fee structures differ across rollups.
A hypothetical rollup cost
Suppose a hypothetical rollup lowers its layer-one cost by posting a batch as a blob. A user's fee may still include execution, operator costs, proof generation, and margin. Do not attribute a lower or higher fee to blob pricing alone; review the protocol's published calculation.
The availability window
The Ethereum protocol requires blobs to be served for a defined period, not forever. Current documentation describes a minimum availability window of roughly 18 days; longer-term access can depend on archival services, rollup operators, or other providers.
What users should verify
Find where data needed for withdrawals or state reconstruction is stored and for how long. In the rollup's decentralization documentation, identify data publishers, verifiers, proof submitters, forced-inclusion routes, and withdrawal waiting periods.
Limits of storage and proof
Data availability indicates that data needed for verification was made available; it does not promise permanent retrieval or privacy. Lower blob costs alone do not establish adequate security. Compare each chain's retention and recovery arrangements.