Ethereum has officially activated the Fusaka upgrade on the mainnet. This marks another important step in the technical evolution of the network. The update went live without a hitch at 4:49 pm ET, according to a summary shared by researcher Christine Kim. After the 225th All Core Developers Execution (ACDE) meeting. For most users, the transition was seamless. However, there was a brief hiccup. About 25% of validators saw a brief drop in participation.
All of them were running the Prysm client. The developers quickly fixed the problem. Within a few hours, validator activity increased again to almost full intensity. A minor Nethermind-Nimbus bug is also being fixed. So far, developers say very few users appear to be affected. In short, Fusaka landed cleanly and the chain was stable.
First automated BPO Hard Fork will be available on December 9
With Fusaka now active, Ethereum developers are moving directly into the next phase of the upgrade. The first automated blob parameters only (BPO) hard fork is scheduled for December 9. This update will automatically adjust the blob parameters without triggering a full traditional hard fork process. It is based on the post-Dencun roadmap and aims to adjust how Ethereum handles data availability for rollups. In simple terms, this change helps Ethereum scale more efficiently. It allows the network to respond faster to real-world demand without repeated manual updates. Developers see this as a key step toward more seamless and adaptive network updates in the future.
Glamsterdam upgrade scope reduced
At the same meeting, developers also moved forward with planning for the next major hard fork, known as Glamsterdam. More than 40 Ethereum Improvement Proposals (EIP) were originally on the table. After some discussion, the developers flatly rejected 14 proposals. They now strongly favor the possible inclusion of five EIPs. Five other proposals remain under active review. The rest will not advance in this update cycle. This pruning reflects an increasing focus on keeping forks firm and manageable. Developers want fewer features per update. This reduces technical risk and improves testing quality. Final decisions on the scope of Glamsterdam will continue during upcoming core developer calls.
FOCIL and holiday calendar updates
The developers also agreed to pause the Ethereum developer meetings on December 25 and January 1 during the holiday period. After that regular calls will resume. Meanwhile, the controversial EIP-7805, also known as Forking Forced Choice Inclusion Lists (FOCIL), remains unresolved. The teams will review this proposal in the next All Core Developers Consensus (ACDC) call. FOCIL could impact how transactions receive guaranteed inclusion during block production, making it a sensitive governance issue.
What this means for Ethereum users
For everyday users, activating Fusaka does not change the current way wallets or apps work. However, it strengthens the reliability of the network and prepares Ethereum for more automated upgrades in the future. The upcoming BPO fork on December 9 will further support accumulations and Layer 2 activity. Meanwhile, Glamsterdam’s more limited scope indicates a more measured upgrade process going forward. In short, Ethereum just locked another clean update. And now that automation reaches the protocol level, the network is quietly shifting toward a faster, more flexible era of development.
The post Ethereum Activates Fusaka as First Automated BPO Fork Set for December 9 appeared first on Coinmania.
