TLDR
Ethereums second blob parameter upgrade (BPO-2) is scheduled for 7 Jan 2026 (UTC), aimed at improving Layer 2 data capacity.
- BPO-2 raises the blob target to 14 and the maximum to 21 per block per a crypto week ahead update.
- The change is intended to lower Layer 2 rollup data costs and improve throughput for Arbitrum, ethereum/">Optimism, and Base, as noted in a market rundown.
Deep Dive
1. Date And Scope
The upgrade is slated for 7 Jan 2026 (UTC) and is the second Blob Parameter Only hard fork, part of Ethereums current scaling roadmap focused on rollup data availability. This timing is cited in a crypto week ahead update.
If you track Layer 2 fees or throughput, 7 Jan is the day to watch for a capacity bump that can affect transaction costs and confirmation times.
2. What Changes
Blobs are data packets introduced to make rollup posting cheaper and more scalable. BPO-2 increases the blob target to 14 and the maximum to 21 per block to expand the bandwidth available to rollups, according to a market rundown.
- More blobs per block mean higher data throughput for rollup proofs and batches.
- Greater capacity generally reduces contention, which can translate to lower effective data fees.
Expect improved headroom for rollup data posting. When block space pressure eases, Layer 2 data fees can drift lower, especially during peak periods.
3. Impact On L2s
Coverage highlights that the upgrade is intended to benefit leading Layer 2s (Arbitrum, Optimism, Base) by reducing rollup transaction costs and improving scalability, as noted in a weekly events summary.
- Lower data costs can improve user transaction fees and dapp economics on L2s.
- Capacity gains help sustain higher activity during busy periods without sharp fee spikes.
If you use L2s regularly, fees could be more stable and lower after the upgrade. For builders, higher throughput supports more frequent batch posting and smoother user experiences.
Conclusion
Ethereums BPO-2 upgrade on 7 Jan aims to expand blob capacity, which should help Layer 2s by lowering data costs and improving throughput. The immediate implication is potentially cheaper and more consistent rollup activity, supporting broader scaling momentum across the L2 ecosystem.
