What changed in ETH block capacity?

TLDR

Ethereum (ETH) raised its per?block blob capacity to 15%%CKPROTECTED2%%, increasing data bandwidth for Layer 2 posting without changing execution gas. This was activated via BPO?1 and did not require a hard fork per a foundation update summary.

1. BPO?1 increased blob slots per block to 15 without a hard fork per an announcement.
2. Higher blob capacity boosts L2 throughput and typically reduces blob fees, supported by the PeerDAS narrative in a technical overview.
3. A follow?up, BPO?2, is planned for January to expand capacity further per the notice.

Deep Dive

1. What Changed

Ethereum added room for more blobs per block, lifting the cap to 15. Blobs are the data containers introduced by EIP?4844 that L2s use to publish transaction data cheaply, separate from normal execution gas. The change was enabled by BPO?1 and did not require a hard fork per a foundation update summary.

2. Practical Impact

More blob capacity translates into higher data throughput and typically lower blob fees for L2s, which can lower end?user costs on those L2s. The PeerDAS track (EIP?7594) and ongoing capacity work are framed as enabling several?times more blob data and cheaper validation overhead, consistent with analysis in a technical overview.

1. Cheaper blob fees often pass through to lower L2 transaction costs and improved batching efficiency.
2. More predictable capacity reduces spikes during peak periods, helping apps that rely on regular posting schedules.
3. Execution gas on Ethereum L1 is unchanged, so core EVM transaction costs do not directly fall from this change.

3. Next Steps and Risks

A second parameter increase, BPO?2, is planned for January to expand block blob capacity further per the notice above. Capacity increases must be balanced against validator bandwidth, storage, and propagation times to avoid network instability during stress.

1. Near?term risk is uneven client or validator performance during capacity shifts, which teams typically monitor and tune.
2. Benefits accrue primarily to L2s; L1 execution remains governed by the gas limit, so swap or contract prices on L1 are not directly impacted.
3. If higher capacity triggers fee competition among L2s, users could see lower costs but also more variance across ecosystems.

Conclusion

Ethereums block capacity for blob data was raised to 15 per block, expanding space for L2s to publish batches and stabilizing their costs and throughput. The next increase (BPO?2) is slated for January, which could further lower L2 fees and improve performance, while core L1 execution gas remains unchanged.