Ethereum Activates Fusaka as First Automated BPO Fork Set for Dec 9

Ethereum has officially activated the Fusaka upgrade on mainnet. This marks another major step in the network’s technical evolution. The upgrade went live smoothly 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 happened without disruption. However, there was a brief hiccup. Around 25% of validators saw a short drop in participation. 

All of them were running the Prysm client. Developers quickly patched the issue. Within a few hours, validator activity climbed back to near full strength. There is also a minor Nethermind-Nimbus bug under review. So far, developers say very few users appear to be affected. In short, Fusaka landed cleanly, and the chain stayed stable.

First Automated BPO Hard Fork Set for Dec 9

With Fusaka now active, Ethereum developers are moving straight into the upgrade’s next phase. The first automated Blob Parameter-Only (BPO) hard fork is scheduled for December 9. This update will automatically adjust blob parameters without triggering a full traditional hard fork process. It builds on the post-Dencun roadmap and aims to fine-tune 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 upgrades. Developers see this as a key step toward smoother, more adaptive network upgrades going forward.

Glamsterdam Upgrade Scope Gets Narrowed

At the same meeting, developers also advanced planning for the next major hard fork, known as Glamsterdam. More than 40 Ethereum Improvement Proposals (EIPs) were originally on the table. After discussion, developers rejected 14 proposals outright. They now strongly favor five EIPs for possible inclusion. Another five proposals remain under active review. The rest will not move forward in this upgrade cycle. This pruning reflects a growing focus on keeping forks tight and manageable. Developers want fewer features per upgrade. That lowers technical risk and improves testing quality. Final decisions on Glamsterdam’s scope will continue over the next several core developer calls.

FOCIL and Holiday Schedule Updates

Developers also agreed to pause Ethereum developer meetings on December 25 and January 1 for the holiday period. Regular calls will resume after that. Meanwhile, the controversial EIP-7805, also known as Fork-choice enforced Inclusion Lists (FOCIL), remains unresolved. Teams will revisit this proposal at the next All Core Developers Consensus (ACDC) call. FOCIL could impact how transactions receive guaranteed inclusion during block production, making it a sensitive governance topic.

What This Means for Ethereum Users

For everyday users, Fusaka’s activation does not change how wallets or apps work today. However, it strengthens network reliability and prepares Ethereum for more automated upgrades in the future. The upcoming December 9 BPO fork will further support rollups and Layer-2 activity. Meanwhile, Glamsterdam’s tighter scope signals a more measured upgrade process going forward. In short, Ethereum just locked in another clean upgrade. And with automation now arriving at the protocol level, the network is quietly shifting into a faster, more flexible era of development.