ACDC #170 came at a moment when the Ethereum community had a lot happening at the same time. Fusaka is almost ready to go live on mainnet, Glamsterdam is moving closer to being wrapped up, and conversations for Heka Bogotá have quietly started in the background.

For the developers on the call, it felt like working on three different timelines at once: finishing one upgrade, settling the next, and already thinking about what follows. The challenge now is to keep everything moving without compromising safety, validator comfort or the clarity of the upgrade process.

• Fusaka Updates
• Glamsterdam Updates
• FOCIL Debate
• EIPs Discussed
• Miscellaneous Updates

Fusaka Updates

Fusaka mainnet readiness was the first topic of the call. Client teams reported that Mainnet Shadow Fork 1 successfully ran both BPO stages, with BPO1 using fifteen max blobs and BPO2 using twenty one max blobs, and the network maintained almost one hundred percent participation for a full day.

Nimbus confirmed that version 25.11.0 performed well, and a corrective release for version 25.11.1 is being prepared to address a supernode bug found during testing. With no blockers and strong confidence from client teams, Fusaka is set for mainnet activation on December 3.

Nethermind is also planning a livestream for the launch. Developers revisited the structured incident response framework introduced during Pectra.

Each client team must submit designated responders, escalation paths, and communication channels to the Fusaka incident plan. Several teams have already submitted entries, while others were reminded to finalize them before launch.

Glamsterdam Updates

As the conversation moved past Fusaka, the focus naturally shifted to Glamsterdam and its main feature, ePBS. Prysm shared that most of its ePBS work is already passing tests and is almost ready to merge.

Teku has been steadily pushing major pieces into master, Lighthouse is making quiet but consistent progress, and Lodestar mentioned that it should be fully ready to participate in Devnet testing by January. With the pressure of Fusaka testing coming to an end, teams expect ePBS work to pick up speed.

The overall sentiment was that Glamsterdam’s Devnet phase is within reach. One area that still needs deeper discussion is trustless payments inside ePBS.

After Devconnect, it became clear that developers were not all viewing this mechanism the same way. Some had concerns about how it behaves in edge cases, others questioned the economic assumptions behind it, and a few simply felt the current design needed more clarity.

Because of this, a dedicated breakout session is now scheduled for December 5. Until that conversation happens and the group reaches shared understanding, Glamsterdam cannot fully lock in its ePBS scope.