Ethereum developers have wrapped up the final chapter of last month’s major Fusaka upgrade.
On Wednesday, Ethereum synced the second “Blob Parameters Only” fork planned for this upgrade cycle, not only improving the data availability, but also showcasing how smaller network updates can be rolled out in phases.
“Instead of waiting for a major annual upgrade to adjust network capacity, BPO forks allow Ethereum to tune specific parameters (like blob targets) independently and efficiently,” the @Ethereum account wrote on X. “This gradual ramp-up allows the network to safely test increased load step-by-step.”
Blobs, introduced in Ethereum’s 2024 Dencun upgrade, are temporary, large chunks of data used by Layer 2 rollups to record batches of transactions cheaply to the mainnet. These data stores, also called “Binary Large OBjects,” are stored for 18 days before being deleted permanently.
Many of Fusaka’s 13 Ethereum Improvement Proposals were focused on improving Ethereum’s data availability layer, including the most notable upgrade to PeerDAS, which allows nodes to verify blob data by checking smaller samples. It also rolled out the BPO mechanism to gradually scale blob limits.
The first BPO activated on Dec. 9, about a week after Fusaka went live, increasing the target blobs per block to 10 from six and the max blobs per block to 15 from nine. Wednesday’s upgrade pushes this target to 14 and max cap to 21.
“More blobs = more data availability for Layer 2 networks,” Ethereum wrote. “By incrementally raising the per-block blob limits, Ethereum reduces data costs for rollups. This helps keep transaction fees on L2s low even as activity grows, ensuring the network scales sustainably with demand.”
© 2026 The Block. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.