Ethereum developers increased BLOB object limit to 21 with BPO fork. On January 7, Ethereum developers implemented the Blob Parameter-Only (BPO) fork on the main network, increasing the limit of BLOB objects from 15 to 21. BPO2 is live! Blob limit is now 21.
The update also increased the target BLOB value from 10 to 14. Each such digital object holds 128 KB of data, meaning an Ethereum block can now store up to 2688 KB (at the maximum allowable value). This allows for more transactions to be processed simultaneously, enhancing blockchain efficiency without directly risking overload. The fork marks the second expansion of BLOB limits since the activation of the Fusaka upgrade.
The previous BPO was implemented on December 9, 2025. The Ethereum team’s initiative aims to expand the throughput of rollups. In addition to scaling layer two, BLOB objects have played a role in curbing base-level fees.
On January 7, Ethereum developers rolled out the Blob Parameter-Only (BPO) fork on the mainnet, raising the limit of BLOB objects from 15 to 21. BPO2 is live, and the blob limit is now 21, with the target BLOB value increased from 10 to 14. Each BLOB object stores 128 KB of data, meaning an Ethereum block can hold up to 2688 KB at the maximum value. This upgrade enhances throughput by allowing more transactions to be processed in parallel, improving blockchain efficiency while reducing the risk of overload.
The fork marks the second expansion of BLOB limits since the Fusaka upgrade activation; the previous BPO was implemented on December 9, 2025. The Ethereum team aims to boost rollup throughput and scale layer two, with BLOB objects also contributing to lower base-level fees. The ongoing evolution reflects Ethereum’s commitment to expanding data capacity and network performance.
Leave a Reply