This is because Ethereum’s weekly All Core Developer call has a lot to take care of.checkpointThe “” series aims for high-level updates approximately every 4-6 weeks, depending on what’s happening in core development. See previous update. here.
If you like reading about the latest in core development, you might want to learn about Forkcast today. Publish call summaries, chats, and transcripts Every core developer call is typically available within a few hours of the call.
teacher:
of Fusaka The upgrade is almost out the doorGramsterdam is currently being implemented with major and minor features determined and enhanced. Discussions regarding the Heca/Bogotá upgrade will begin soon.
If you’d like to submit your thoughts on what minor features Gramsterdam should include, now’s the time. There is still no consensus on whether the Anti-Censorship Transaction Feature (FOCIL) will definitely be included or be deferred to a later upgrade. If you have a big feature you would like to propose for Ethereum, headliner Suggestions for discussion on upgrading Heca/Bogotá. It is likely to start in early 2026.
It’s Devconnect week! Progress may be slower than usual over the next two weeks. On the other hand, face-to-face discussions may accelerate the decision-making of Gramsterdam.
Fusaka
Testing for this next upgrade is complete. Fusaka and both BPO fork It ran successfully on all three major testnets with few issues. Due to historical background, the testnet fork went much more smoothly than they generally do In these Ethereum upgrades. Some clients are still experiencing small issues, but this won’t delay the upgrade as consensus isn’t important.
Fusaka will go live on December 3rd at 21:49 UTC. watch party will be streamed From the Ethereum Protocol YouTube channel. Node operators must be updated by then to remain compatible with the network after the upgrade. For an overview of its features, Mainnet announcement blog post And even more ethereum.org.
timeline
Note for node operators: Fusaka compatible client release Contains configuration for all three forks: Only one update is required for a successful upgrade.
| event | Time (UTC) | target blob | max blob |
|---|---|---|---|
| Fusaka Main Net | 2025-12-03 21:49 | 6 (no change) | 9 (no change) |
| BPO fork 1 | 2025-12-09 14:21 | 10 | 15 |
| BPO fork 2 | 2026-01-07 01:01 | 14 | twenty one |
glamsterdam
With Fusaka retired, the focus is now on future upgrades. Immediately after Fusaka, glamsterdam The company is aiming for “sometime in 2026.” Its main characteristics (“Headliner”), enshrines the separation between proposer and builder (ePBS) and Block-level access list (BAL) was chosen for August, and the minor (“non-headline”) feature is currently being discussed.
When the Pectra fork was scoped to 2024, the upgrade timeline was fairly flexible, and the overloaded fork had to be split in two because the upgrade didn’t have a clear headliner. In response, ACDE call facilitator Tim Beiko said, proposed a clearer and more rigorous structure Determine the scope of upgrades to optimize your processes.
This is the first upgrade ever made. Clear schedules and deadlines As a result, it now offers far more features than before. The deadline to propose non-headline features was October 30th. 48 features Suggested in time. Core developers and the community are currently reviewing this list to decide which to prioritize. Features are selected based on overall need/urgency, compatibility with other features, and level of complexity.
if One of these features With particular urgency for users of the core protocol, the Ethereum community is asked to: There’s a chime So that core developers understand the need for it.
Forcil
While the headliner process encouraged the community to select only one feature each for the execution and consensus layers for simplicity, the censorship-resistant feature Forked Choice Forced Inclusion List (FOCIL) received such strong support that it was moved to conditional.considered” status and the two selected priorities have been moved to “ ” status.scheduled“status. was discussed This is dependent on the progression of ePBS (consensus layer functionality, and to some extent BAL (execution layer functionality)), and also requires that FOCIL does not significantly slow down the upgrade.
in All Core Developer of the Weekthere was support for FOCIL’s transition to upgrades following Gramsterdam and Heca/Bogota. conditional Whether it will be included in that upgrade has not yet been determined. This decision allows developers to better know if they can work on small features, so they don’t have to wonder if they should be scoped with FOCIL in mind.
timeline
There is still no proposed schedule for Gramsterdam beyond “sometime in 2026.” It depends on the total scope of features selected and the progress of the headliner. The final set will likely be determined by the end of this year, after which developers can focus on implementation and selecting key features for the next upgrade.
This week is Devconnect week. In other words, by having a direct conversation, All core development execution calculations for next weekHowever, the next two Monday test calls will be cancelled.
gas limit
All clients confirmed 60M readiness by Fusaka. Node operators do not need to take any action other than normal client updates before Fusaka. All clients default to 60M. It is currently expected that the default values for periodic gas limits will continue to increase. There is an established framework By Nethermind for thinking about safe limits on targets. Node operators can always signal support for higher values by: Configure manually their limits.
Heca/Bogota Upgrade
With the rhythm established of planning one fork while implementing the other, we can start discussing the headline features of the Heka/Bogotá upgrade once Fusaka is published. Heka was chosen as a star name, and portmanteau word Still under discussion. After this week’s All Core Devs call, we expect FOCIL to be the frontrunner in the headliner selection process.
Fusaka has been in tension between two delivery priority strategies: ship safely and ship quickly. The community is pushing for faster forks, and it shows in their decision-making. As a result of our focus on speed, Fusaka ships 6 months and 26 days after Pectra. Past fork dates are typically chosen based on when all With the client ready, Fusaka’s timeline tilted towards the date. largely The client was ready.
Fusaka’s preparation had unique advantages. In some ways, the implementation had a head start as its key features were originally part of Pectra before the upgrade was split in two. We cannot expect the same timeliness with Gramsterdam, but we do expect there will still be an effort to ship as quickly as possible.
If this new structured process pioneered in the Glamsterdam upgrade is less confusing, less stressful, and more efficient than Pectra, then it’s clear that it’s in your best interest to plan for the long term and define structure at each step of the upgrade, rather than just pushing developers to react quickly. You can then move on to experiment with better parallelizing planning and development for future forks.
But if Glamsterdam still feels as underwhelming as Pectra initially felt, it needs to find a way to more effectively rein in its enthusiasm for introducing a broader feature set and the “can-do-it-all” mentality at the start of an upgrade.
If FOCIL is moved to Heka/Bogotá: 2 It is difficult to commit to features clearly in a post-fork upgrade. I’ve learned in the past that this is an unfairly problematic process where a feature is scheduled, but the community has moved on from the desire to implement it, forcing developers to remove it when they’ve planned it and already started work on it.
As we move to the next upgrade, the best the developers and community can do for FOCIL is to continue to actively support its rapid inclusion and not move on to shiny new major features that could undermine its perceived urgency. Censorship resistance is critical to Ethereum’s fundamental values, and it is important that we do not lose it even as other exciting features gain a strong narrative.
Related ACD calls:
(October 2nd – November 13th)
ACDT: 61, 60, 59, 58, 57, 56
ACDC: 169, 168, 167, 166
ACDE: 224, 223, 222
