Fusaka blob throughput versus Dencun: 50 percent increase

The Ethereum mainnet currently processes data blobs at a rate of 2,048 kilobytes per slot under the Dencun upgrade. This figure represents a significant jump from the pre-Dencun baseline but remains constrained by the current protocol limits. The upcoming Fusaka upgrade targets a specific increase in this capacity to support growing Layer 2 demand. Developers and validators must understand the precise delta between these two states to plan for future network load. The transition involves changing the "max_blobs_per_slot" parameter, which directly dictates how much off-chain data can be attached to each block.

The Dencun baseline

Dencun introduced EIP-4844, which established the current standard for blob transactions. Under this specification, each slot contains exactly 6 blobs. Each individual blob has a fixed size of 131,072 bytes, which equals 128 kilobytes. Multiplying the number of blobs by their size yields the total throughput of 2,048 kilobytes per slot. This limit applies to all Layer 2 networks that rely on Ethereum for data availability. The design prioritized stability and gradual adoption over immediate maximum capacity. Validators were required to store only the KZG commitments for these blobs, not the full data, which reduced storage overhead significantly. However, the 2,048 KB cap has become a bottleneck as transaction volumes on major rollups have increased steadily since the upgrade went live.

The Fusaka target

Fusaka proposes raising the "max_blobs_per_slot" value from 6 to 9. This change increases the total data capacity per slot to 3,072 kilobytes. The calculation is straightforward: 9 blobs multiplied by 128 kilobytes per blob equals 3,072 KB. This represents a 50 percent increase in raw data throughput compared to the Dencun baseline. The upgrade does not change the size of individual blobs, so the unit of measurement remains constant. Only the count of allowed blobs per slot changes. This adjustment aims to alleviate congestion without requiring complex changes to the consensus layer. It allows Layer 2s to post more data in the same time frame, reducing the need for expensive alternative data availability solutions. The protocol assumes that validators can handle the slightly higher verification load associated with processing three additional KZG commitments per slot.

Implications for scaling

The shift from 2,048 KB to 3,072 KB per slot provides clear headroom for existing rollups. For instance, if a Layer 2 posts 1,500 KB of data per slot today, it utilizes roughly 73 percent of the available Dencun capacity. Under Fusaka, that same volume would consume only 49 percent of the new capacity. This reduction in utilization ratios improves network resilience against sudden spikes in activity. However, the increase is linear, not exponential, meaning it solves near-term congestion rather than long-term scalability challenges. Validators must update their software to recognize the new limit before the fork activates. Failure to do so could result in rejected blocks or missed rewards during the transition period. The community debate continues on whether 9 blobs are sufficient or if further increases should be planned for subsequent upgrades. Will 3,072 KB per slot prove adequate for the next wave of decentralized application growth?