The failure of Pectra’s blob capacity expansion

The mismatch in blob pricing

The August 22 event where Base experienced 40 higher-tip transactions demonstrates how the mismatch between the target of 6 blobs and the effective demand range of 6.57 to 6.72 blobs prevents stable pricing. This instability stems from the Pectra upgrade parameters which set the target at 6 blobs and the maximum at 9. The mismatch between the target of 6 blobs and the effective demand range of 6.57 to 6.72 blobs means the market cannot reach equilibrium when the average number of blobs per block stays at 6. I find the current pricing model broken because it fails to discover a fair price when usage sits near the target. Base batchers and transaction managers require predictable costs to maintain reliability. The target demand paradox explains why the fee market remains in a state of inefficiency. Even when average usage approximates the target, the market fails to reach equilibrium if the demand variance is high. Because the effective demand range falls between 6.57 and 6.72 blobs, the market cannot reach equilibrium even when average blob consumption approaches the target value of 6. The current mechanism fails to discover a fair price for blob space because the target value falls outside the range of effective demand. L2 teams identified the August 22 event as a specific investigation target.

Data capacity and node pressure

Rollups purchased 25,600 blobs daily in the five days following the Pectra activation in May 2025. This amount exceeds the 21,200 daily blobs from the 60 days leading into the upgrade. Despite this growth, the average number of blobs per block stays 33% below the new target of 6. This gap allows blobs to remain virtually free, with rollups paying less than one-thousandth of a penny daily. Total blob object costs since Pectra went live reached only four-thousandths of a penny. Post-Pectra, blobs are 86% full on average, compared to 82% in the 60 days before the upgrade. The upgrade increased daily data capacity from 5.5GB to 8.15GB, yet only 3.3GB of dataspace is currently purchased. This equals 40% of the maximum capacity and 61% of the target rate. Before the upgrade, rollups purchased 99% of the target rate and 50% of the total capacity. This is a difference of 2.7 gigabytes of data capacity purchased daily pre-upgrade against 3.3GB today. Consensus layer nodes must hold rollup blob data for at least 18 days, and they now carry an estimated 44.6GB of unpruned data. This rise is from the 40GB to 44GB range seen before the upgrade. If demand reaches the target rate, nodes must carry between 95GB and 100GB of data. Will the increased data load eventually force a change in how validators handle pruning?

Proposed fee market adjustments

The community proposes several changes to fix these issues. EIP-7762 suggests raising the minimum base fee from 1 wei to 2^25 wei to accelerate price discovery. At a base fee of 1 gwei, it takes 190 blocks for the fee to climb from 1 to 5 gwei. With the new minimum, that duration drops to 42 blocks. EIP-7918 intends to resolve the decoupling of fee markets by ensuring the blob base fee remains responsive to the cost of execution gas during periods of high demand. You should monitor how these changes interact with the L2 posting reliability. Base needs to test deadline-aware replacement policies and batch packing to lower all-in posting fees. This matters because the L1 gas limit rose from 30 million to 60 million in 2025. Researchers also suggest that the current pricing mechanism fails to account for the liveness risk of including blobs during periods of high congestion.