- Ethereum Fusaka Upgrade completes on mainnet, lifting the gas limit to 60 million and easing block space pressure for users.
- PeerDAS introduces data sampling so nodes handle smaller pieces of blob data while rollups gain higher and more stable throughput.
- A new minimum blob base fee links blob pricing to execution gas, keeping rollup data costs aligned with network usage.
The Ethereum Fusaka Upgrade went live on mainnet on Wednesday, December 3, 2025, at 21:49:11 UTC, marking a new phase in how the network handles data and block capacity. At epoch 411392, validators switched to the new rules that raise the gas limit, activate PeerDAS, and adjust the economics of blob usage for rollup ecosystems that rely on Ethereum as a settlement layer.
Timeline and scope of the Ethereum Fusaka Upgrade
Fusaka takes its name from a blend of “Fulu” and “Osaka,” which stand for the consensus and execution layer components of the release. The hard fork follows May 2025’s Pectra upgrade and continues the roadmap that aims to scale rollups while keeping the base layer relatively simple and stable. Developers activated the upgrade at the start of epoch 411392, which aligns with slot 13,164,544 on December 3, 2025, at 21:49:11 UTC, after several testnet rehearsals on Hoodi, Holesky, and Sepolia. The Ethereum Fusaka Upgrade raises the default gas limit on mainnet blocks to 60 million, up from the previous level near 30–40 million, and introduces changes that focus on blob throughput rather than only execution gas. PeerDAS, short for Peer Data Availability Sampling and defined in EIP-7594, becomes active and enables a fourfold increase in blob capacity from the initial Dencun parameters, with later Blob Parameter Only forks scheduled to push blob targets further to 10 and 14 per block and maximums of 15 and 21. Fusaka also reduces node synchronization overhead by roughly 530 GB through protocol clean-ups and introduces 32-slot proposer lookahead, which lets validators see upcoming proposal duties earlier and plan operations more smoothly.
PeerDAS and data availability for rollup ecosystems
Before Fusaka, nodes needed to download entire blob files to check that rollups had posted their data correctly, which placed a heavy load on bandwidth and storage for any operator that wanted to stay in sync. PeerDAS changes this pattern by letting nodes verify data availability through many small, random samples drawn from different peers in the network instead of full downloads. When enough independent samples match, nodes can treat the blob as available without storing or re-downloading every byte. This sampling model lets the network increase blob throughput without forcing each validator to scale its hardware at the same pace. Rollup projects such as Base, Arbitrum, Optimism, and zkSync send their transaction data to Ethereum as blobs, so a higher and more flexible blob capacity directly affects their ability to handle user activity during busy periods. Developers estimate that the expanded blob space and PeerDAS together can support up to eight times more effective data throughput for rollups compared with pre-Fusaka conditions, while keeping per-node bandwidth broadly in line with earlier requirements.
Economic effects of the Ethereum Fusaka Upgrade on blob fees and ETH value
Alongside the technical changes, the Ethereum Fusaka Upgrade modifies how blob fees respond to demand through EIP-7918, which adds a minimum blob base fee linked to execution gas. Under this rule, the protocol compares each blob’s fee to the main execution base fee and enforces a floor at roughly one-sixteenth of that value, preventing blob prices from sinking toward zero when the chain is quiet.
This design answers a concern that first appeared after the Dencun upgrade, when blob fees occasionally dropped so low that they no longer reflected the resource cost of providing data availability. In those periods, the link between network usage, blob demand, and ETH burn weakened, which created uncertainty for both stakers and rollup operators trying to model their long-term costs. By bounding blob fees with a reserve mechanism, Fusaka redirects more value to ETH stakers, makes rollup data costs more predictable over time, and preserves a clearer relationship between layer-2 activity and ETH’s underlying fee revenue. Market analysts have described Fusaka as an infrastructure-heavy release that may not feed into price charts immediately but instead sets base conditions for later growth in rollup usage. Bitwise analyst Max Shannon framed the release as the kind of network upgrade that often looks modest at launch but later appears central once higher rollup throughput and steadier blob fees show up in the data.
Network capacity, node operations and what follows Fusaka
With the higher gas limit of 60 million per block and the re-priced execution paths in EIP-7883, EIP-7823, and EIP-7825, Ethereum can carry more transactions while limiting single transactions to 16,777,216 gas, which is 2²⁴. That cap reduces the chance that one complex call consumes most of a block and helps maintain steady inclusion for ordinary transfers and contract calls during peak periods. Because PeerDAS and the protocol clean-ups lower synchronization overhead by about 530 GB and remove some legacy fields, node operators do not need to upgrade their hardware at the same rate as throughput expands. The Ethereum Fusaka Upgrade also prepares the chain for more flexible blob management through Blob Parameter Only forks, defined in EIP-7892. These config-only changes let developers adjust blob targets and maximums without a full hard fork, which helps match capacity to real rollup demand in a gradual way. Over the coming year, core contributors expect the combination of a 60 million gas limit, more efficient cryptographic pricing, and expanded blob space to roughly double the network’s effective transaction capacity compared with pre-Pectra conditions, while keeping block validation within reach for solo stakers and smaller operators. The Ethereum Foundation has asked client teams, validators, and infrastructure providers to track network performance closely in the first 24 hours after activation. They plan to watch block propagation times, missed proposals, blob utilization, and node health metrics to confirm that the new data availability model behaves as intended under live conditions. Early signs from explorers and client dashboards show stable participation across major clients and normal finality, suggesting that the release integrated smoothly into the existing validator set.
Conclusion
Fusaka brings together higher gas limits, PeerDAS sampling, a revised blob fee floor, and cleaner synchronization rules in a single coordinated step, giving Ethereum a wider path for rollup growth without a matching rise in node costs. The Ethereum Fusaka Upgrade links blob pricing more tightly to execution activity, expands data throughput for rollups, and simplifies life for validators through reduced storage needs and clearer proposer scheduling. Over time, its effects are likely to show up in cheaper and more reliable layer-2 transactions rather than sudden moves in headline metrics on the day of activation, but the structural shift in how Ethereum handles data availability and block capacity is already in place.
Disclaimer
The information provided in this article is for informational purposes only and should not be considered financial advice. The article does not offer sufficient information to make investment decisions, nor does it constitute an offer, recommendation, or solicitation to buy or sell any financial instrument. The content is opinion of the author and does not reflect any view or suggestion or any kind of advise from CryptoNewsBytes.com. The author declares he does not hold any of the above mentioned tokens or received any incentive from any company.
Featured image created by AI
