Express

Ethereum Completes Final BPO Fork of Fusaka Upgrade, Further Enhancing Data Availability Cap

Summary: According to reports, Ethereum developers have completed the second and final 'Blob Parameters Only (BPO)' fork planned during the Fusaka upgrade cycle. This update increases the target number of blobs in a block from 10 to 14, and the cap from 15 to 21, aiming to further enhance the network's data availability capabilities. The BPO ...

According to reports, Ethereum developers have completed the second and final 'Blob Parameters Only (BPO)' fork planned during the Fusaka upgrade cycle. This update increases the target number of blobs in a block from 10 to 14, and the cap from 15 to 21, aiming to further enhance the network's data availability capabilities. The BPO mechanism allows Ethereum to independently adjust key parameters like blobs in stages without waiting for large annual upgrades, gradually testing and releasing network capacity in a more controlled manner. Blobs were initially introduced in the 2024 Dencun upgrade to provide low-cost data storage for Layer2 Rollups, with this data automatically cleared after approximately 18 days on the mainnet. This adjustment is seen as the final step of the Fusaka upgrade. Developers note that with the gradual increase in the single block blob cap, Ethereum can provide more data space for Layer2 networks, helping to maintain stable transaction costs for Rollups amid on-chain activity growth. (The Block)

Last Update:

Tags:
Link: Ethereum Completes Final BPO Fork of Fusaka Upgrade, Further Enhancing Data Availability Cap   [Copy]
  • The Road to 2026: Where Is the Web3 Ecosystem Heading Next? December 7, 2025
  • Vishwa Advances Agentic Infrastructure Research Through Contribution to Emerging Framew... November 22, 2025
  • BitMart US Launches Operations with 49-State Licensing and Zero-Fee Program November 17, 2025
  • Global Financial Giants Enter Stablecoin Arena in Pivotal Shift October 30, 2025
  • CRYPTO'S NEW PLAY: 24/7 STOCK TRADING October 29, 2025
  • You need to login to comment.