TLDR
Ethereum (ETH) Fusaka upgrade is scheduled for 3 Dec (UTC), confirmed by ecosystem posts and media coverage Base team post and a Bitcoinist report.
- Focus: scale L1 data via blobs and PeerDAS to lower Layer?2 costs Ethereum roadmap note.
- Capacity: coverage points to larger blob capacity, with eightfold estimates in recent updates Yahoo Finance roundup.
- Rollout: BPO forks enable gradual blob limit increases after the Dec 3 cutover developer summary.
Deep Dive
1. Date And Confirmation
The upgrade date cited across the ecosystem is 3 Dec (UTC). Bases engineering update references the Ethereum Fusaka upgrade on Dec 3 and aligns internal scaling plans to it Base team post. Media coverage matches this timing, stating Fusaka Upgrade set to take place on December 3 %%CKPROTECTED1%%. The official Ethereum account frames it as a December roadmap milestone and directs readers to the roadmap page Ethereum roadmap note.
Treat 3 Dec as the operational target date. Final client releases and network coordination typically surface close to cutover, so watch the official feed above.
2. What Changes
Fusaka centers on L1 data scaling for Layer?2s via blobs and PeerDAS. PeerDAS lets nodes verify sampled blob data rather than full chunks, enabling more blobs per block and cheaper data availability for L2s developer explainer. Some coverage also mentions Verkle Trees and a larger block gas limit (from 45M to 150M) as part of the package, aiming at throughput and storage efficiency Bitcoinist report.
If blobs per block rise, L2s like Arbitrum, Base, and Optimism could see structurally lower costs. Users should expect cheaper L2 transactions and improved capacity.
3. Capacity And Rollout Mechanics
Post?upgrade, blob capacity is expected to increase materially. One round?up cites eightfold blob capacity expansion in December Yahoo Finance roundup. Developers also describe BPO forks that let blob limits ratchet up progressively, with capacity more than doubled by early January developer summary. Broader ecosystem posts frame Fusaka as a key step in Ethereums scaling roadmap Ethereum roadmap note.
Expect staged capacity increases rather than a single jump. Monitor client release notes and post?fork telemetry for the actual blob limits applied over December and January.
Conclusion
Fusaka targets 3 Dec (UTC) with an emphasis on blob?based data scaling that should cut L2 costs and raise throughput. The date is widely echoed by ecosystem teams and media, while official messaging positions it as a December roadmap milestone. Practical effects will depend on the realized blob limits and client readiness in the weeks after cutover.
