01

Why did rollup fees suddenly fall?

Layer 2 rollup fees dropped sharply after a 2024 Ethereum upgrade. Rollups must record transaction data on Ethereum, and that cost had been a large share of their fees. The upgrade introduced blobs, a new kind of data space, and cut that cost dramatically.

Blob data does not stay on Ethereum forever, though; nodes can delete it after a set period. Below, we cover what blobs carry and how they differ from the earlier approach, what the retention period means for users, and what is needed for verification and withdrawals afterward, using a hypothetical cost comparison.

02

What a blob carries

EIP-4844 defines blobs, large chunks of data attached to transactions and propagated alongside Ethereum blocks. Each blob is about 128 KB, and rollups use them to post batches of transactions. Ethereum's execution layer does not read blob contents directly; blocks keep only a short cryptographic commitment representing them.

Blobs have their own fee market. Blob gas is priced separately from regular gas according to demand, so blob costs can stay relatively stable when ordinary transactions are congested, or spike on their own when demand for blob space surges.

03

How blobs differ from calldata

Before blobs, rollups posted data as calldata, the input field of ordinary transactions. Calldata is kept permanently by every Ethereum node and can be read by smart contracts, which makes it expensive. Blob data cannot be read by contracts and is deleted after a period, which makes it far cheaper.

As Ethereum.org's page on data availability explains, what rollups need is for data to be published so anyone can obtain it for a period, not stored forever. If anyone can download the data during that window to verify or archive the rollup's state, data availability has done its job.

04

A hypothetical cost comparison

The table compares posting about 100 KB of data, a batch of 1,000 transactions, as calldata versus as one blob. It assumes 16 gas per byte of calldata at 20 gwei, and a blob gas price of 10 gwei. Real blob prices vary widely with demand.

Cost of posting 100 KB of data (hypothetical)
MethodGas usedAssumed gas priceCost per batchCost per transaction
Calldata≈ 1.6 million gas20 gwei≈ 0.032 ETH≈ 0.000032 ETH
One blob131,072 blob gas10 gwei≈ 0.0013 ETH≈ 0.0000013 ETH

Under these assumptions, the blob is about 25 times cheaper. When blob demand surges its price can rise quickly, so the gap changes over time.

05

The availability window

Under EIP-4844, Ethereum's consensus nodes keep blob data for 4096 epochs, roughly 18 days, after which they may delete it. The commitment in the block remains permanently, but the actual data can no longer be retrieved from ordinary nodes after that window.

The 18 days are set longer than an optimistic rollup's roughly seven-day challenge period, so anyone can obtain the data and prove an incorrect state within that time. The window guarantees time to confirm and verify that data was published; it is not a promise to store it forever.

06

What is left for users to check

After 18 days, recomputing a rollup's past state requires someone, such as the rollup operator, block explorers, or archival services, to have kept the data. Ordinary users rarely need to store blobs themselves, but it is worth knowing who could reconstruct the state needed for withdrawals if the rollup stopped operating.

Rollups generally need only the current state to process withdrawals, so old blobs disappearing does not immediately put user funds at risk. Who keeps the data matters when you want to verify old transactions independently or when a long-stopped rollup's state must be rebuilt.

Ethereum.org's layer 2 overview notes that different rollups make different trade-offs on data and security, so the answer to who keeps historical data, and for how long, is specific to each network.

07

What to check

Check how a rollup you use handles its data.

  1. Find in the official documentation whether the rollup posts data as blobs, as calldata, or to an external data availability layer.
  2. In a block explorer, see whether the rollup's batch transactions include blobs and how often they are posted.
  3. Compare the roughly 18-day blob retention window with the rollup's challenge period or proof interval.
  4. Look for who stores data after the window and whether the documentation explains how to rebuild state if the operator stops.
  5. Check how the rollup's fees behaved during past spikes in blob prices to gauge fee volatility.
08

Limits of storage and verification

Blobs publish data cheaply and securely, but long-term storage is left to parties outside Ethereum. If all of them deleted the data, independently re-verifying past state could become difficult. Further upgrades to expand blob capacity continue to be discussed, so details depend on timing.

The cost comparison uses hypothetical gas prices. For a real rollup, check the EIP-4844 specification, Ethereum.org, and the rollup's current documentation, paying attention to publication dates.