Last week I did what I do every quarter as part of my audit routine: I pulled block explorer data for the twenty largest rollups and measured how much blob space they actually consume against how much they provision. The result stopped me. The median rollup on that list used less than 12% of the data availability capacity it had resold to its users. One well-funded Layer 2, fresh off a nine-figure DA partnership announcement, had not posted a single blob above 40% saturation in the entire preceding month. Its token was up 60% since the deal closed.
The market is bidding up data availability as the scarce resource of the next cycle. The on-chain evidence says something quieter and more uncomfortable: we built the cathedral before the saints arrived.
I want to be careful, because "DA is overhyped" has become a lazy take, and lazy takes lose money. My position is narrower and, I hope, more useful. It is not that data availability does not matter. It is that the pricing of DA — in tokens, in partnerships, in the valuations attached to both — has detached from the consumption of DA. In a bull market, that gap is precisely what narrative papers over until it cannot.
To understand why, remember what EIP-4844 actually did. Before proto-danksharding, every rollup that wanted cheap settlement had to publish its state diffs as calldata, paying Ethereum's full execution price for bytes that no one would ever execute. The March 2024 upgrade introduced blobs: a separate, temporary data channel the execution layer never touches and that gets pruned after roughly eighteen days. Blobspace was supposed to be the thing rollups fought over. For a few weeks after launch, they did. Average utilization spiked, fees briefly behaved like a real market, and an entire category of tokens priced themselves on the assumption that demand would run perpetually ahead of the supply of blockspace.
Two years on, supply grew and demand did not keep pace. Ethereum now targets a far larger blob count per block than it did at launch, and the dedicated DA tokens have been repriced through a combination of inflation schedules and a simple physical fact: a rollup only produces as much data as its users generate. That is not a marketing problem you fix with a partnership. It is an arithmetic problem.
Here is the arithmetic, and this is where fifteen years of watching cycles earns its keep. Take a healthy rollup doing four million transactions a month. Strip out the cheap ones — airdrop claims, bot arbitrage, sybil spray — and you are left with maybe a fifth of that volume carrying genuine state changes. Compress those diffs with standard zk or optimistic encoding and you are looking at a few hundred megabytes a month of true payload. One modern blob carries 128 kilobytes. Even generous assumptions put a busy rollup's real DA need well under a dozen blobs a day. Most of the rollups I examined posted fewer than that. Some posted one.
Meanwhile every dedicated DA layer was architected for a world where that number was ten or a hundred times larger. Celestia's design assumes a cosmos of rollups saturating its blockspace. EigenDA's economics assume restakers earning fees on throughput that has not materialized. The newer entrants price their tokens against a demand curve drawn during the euphoria of 2024 and never revised. When I map provisioned capacity across the sector against measured consumption, the mismatch is not a rounding error. It is an order of magnitude, and it widens every quarter as emissions expand supply faster than usage expands demand.
This is why I have stopped reading DA announcements as technology news and started reading them as financing news. A nine-figure DA partnership tells you a treasury locked in future capacity at a discount. It does not tell you users are arriving. The ledger remembers what the market forgets: capacity purchased is not capacity used, and a pre-purchase is a bet on a demand curve, not a measurement of it.
Consider one concrete case from my audit. A mid-cap rollup I reviewed had budgeted for dedicated DA from an external provider, migrated its settlement there, then discovered its own throughput barely touched the provisioned tier. It was paying a fixed monthly commitment for capacity it would not fill for years. The engineering team knew this; the treasury had signed the deal before the load was even measurable. That is not a technical failure. It is a purchasing decision made on narrative, and it is being replicated across the sector right now.
I learned a version of this lesson the hard way, with a much smaller mistake. During the 2020 DeFi summer I ran weekly readability sessions for community members trying to navigate Uniswap and Aave, and I watched how quickly a subsidized yield farm could manufacture the appearance of demand. Turn off the incentive and the users vanish. The same mechanism runs at the infrastructure layer. A DA layer can subsidize its own utilization with tokens, and the dashboards will glow. But data does not lie about its own size, and neither, eventually, does the fee.
There is a macro layer underneath this that institutional clients keep asking me about. ETF inflows have changed who owns the marginal bitcoin, but they have not changed how much data a rollup generates. The post-ETF era gave us a cleaner bridge between traditional liquidity and on-chain settlement, and the honest reading of that bridge is that capital is concentrating in the few assets with real fee streams. Pure capacity plays do not have those streams. They have commitments.
Here is the contrarian angle, stated precisely, because consensus is forming around the opposite view. The standard bull thesis says DA is the bottleneck, that modularity unbundles the stack, and that whoever wins the data layer wins the next decade. I think that inverts cause and effect. Data availability is not scarce; it is abundant and getting cheaper, which is exactly why it cannot command durable rent. The scarce resource was never blobspace. It was trustworthy settlement, credible neutrality, and the willingness of real users to put real value on-chain. Those do not scale with a storage contract. Code is law, but trust is the currency, and trust does not care how many megabytes you can prune.
What decouples first in a cycle like this is not price from value, a tired observation, but infrastructure from usage. We are funding a decade of data capacity against a year of demand, and the accounting will eventually reconcile. That reconciliation is not a crash. It is a slow repricing in which the strongest settlement layers keep their rent and the pure DA plays discover they are selling a commodity. Commodities do not hold narratives, and narratives are what carried these tokens here.
So watch the utilization dashboards, not the announcement headlines. The rollups that survive the next two years will be the ones whose blobs are full because their users are real, not because their treasury bought the space. Stability is a myth; liquidity is the only truth. And liquidity, unlike storage, cannot be provisioned ahead of demand. It has to be earned.

