{"id":17394,"date":"2026-02-18T11:41:44","date_gmt":"2026-02-18T11:41:44","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/02\/18\/checkpoint-7-nov-2025-ethereum-foundation-blog\/"},"modified":"2026-02-18T11:41:44","modified_gmt":"2026-02-18T11:41:44","slug":"checkpoint-7-nov-2025-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/02\/18\/checkpoint-7-nov-2025-ethereum-foundation-blog\/","title":{"rendered":"Checkpoint #7: Nov 2025 | Ethereum Foundation Blog"},"content":{"rendered":"


\n<\/p>\n

\n

Ethereum\u2019s weekly All Core Developer calls are a lot to keep up with, so this “Checkpoint<\/a>” series aims for high-level updates roughly every 4-6 weeks, depending on what\u2019s happening in core development. See the previous update here<\/a>.<\/em><\/p>\n

\"\"<\/p>\n

If you enjoy reading core development updates, you may also be keen to learn that Forkcast now publishes call summaries, chats and transcripts<\/a> for each All Core Devs call, usually available within a couple hours of the call.<\/p>\n

<\/g><\/svg><\/a>tl;dr:<\/h2>\n

The Fusaka<\/a> upgrade is nearly out the door<\/a>, Glamsterdam is ramping up, with its major features in implementation and minor features being decided on. Conversations around the Heka \/ Bogot\u00e1 upgrade will begin soon.<\/p>\n

If you\u2019d like to give your input on which minor features to include in Glamsterdam, now is the time. There\u2019s not yet consensus on whether or not the anti-censorship transaction feature (FOCIL) will definitely be included or delayed to a later upgrade. If you have a large feature you\u2019d like to propose for Ethereum, you should start preparing your headliner<\/a> proposal for the Heka \/ Bogot\u00e1 upgrade discussion, likely to kick off in early 2026.<\/p>\n

It’s Devconnect week! Slower-than-usual progress for the next two weeks is possible. On the other hand, in-person discussions could accelerate decisiveness for Glamsterdam decisions.<\/p>\n

<\/g><\/svg><\/a>Fusaka<\/h2>\n

Testing for this upcoming upgrade is complete, with Fusaka<\/a> and both BPO forks<\/a> having successfully gone live on all three major testnets with very few issues. For historical context, the testnet forks went much more smoothly than they generally do<\/a> with these Ethereum upgrades. While some clients are still seeing small issues, they are not consensus-critical and will therefore not delay the upgrade.<\/p>\n

Fusaka will go live on December 3rd at 21:49 UTC & a watch party will stream<\/a> from the Ethereum Protocol youtube channel. Node operators must update before that time to remain compatible with the network after the upgrade. An overview of its features can be found in the mainnet announcement blog post<\/a> and on ethereum.org<\/a>.<\/p>\n

<\/g><\/svg><\/a>Timeline<\/h2>\n

A note for node operators: the Fusaka-ready client releases<\/a> contain configurations for all three of the following forks. Only one update is needed to correctly follow the upgrades.<\/p>\n

\n\n\n\n\n\n\n\n
Event<\/th>\nTime (UTC)<\/th>\nTarget blobs<\/th>\nMax blobs<\/th>\n<\/tr>\n<\/thead>\n
Fusaka mainnet<\/strong><\/td>\n2025-12-03 21:49<\/td>\n6 (unchanged)<\/td>\n9 (unchanged)<\/td>\n<\/tr>\n
BPO fork<\/a> 1<\/strong><\/td>\n2025-12-09 14:21<\/td>\n10<\/td>\n15<\/td>\n<\/tr>\n
BPO fork<\/a> 2<\/strong><\/td>\n2026-01-07 01:01<\/td>\n14<\/td>\n21<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

<\/g><\/svg><\/a>Glamsterdam<\/h2>\n

With Fusaka wrapping up, focus is shifting toward future upgrades. Directly following Fusaka, Glamsterdam<\/a> is aiming for \u2018some time in 2026\u2019. Its major features (\u201dheadliners\u201d), enshrined Proposer-Builder Separation<\/a> (ePBS) and Block-level Access Lists (BALs)<\/a> were chosen in August while the minor (\u201dnon-headlining\u201d) features are currently being debated<\/a>.<\/p>\n

When the Pectra fork was scoped in 2024, the upgrade timeline was fairly flexible and the upgrade didn\u2019t have a clear headliner, which resulted in an overburdened fork that had to be split in two. In response to this, the ACDE call facilitator Tim Beiko proposed a clearer, more strict structure<\/a> to scoping an upgrade in order to optimize the process.<\/p>\n

This is the first upgrade that has had a clear timeline and deadlines<\/a> from the start, resulting in a much larger number of features being proposed than in the past. The deadline to propose non-headlining features was October 30th, with 48 features<\/a> proposed in time. Core developers and the community are currently reviewing this list to determine which of these should be prioritized. Features will be chosen based on overall need \/ urgency, compatibility with other features, and their levels of complexity.<\/p>\n

If one of these features<\/a> is particularly urgent for users of the core protocol, the Ethereum community is asked to chime in<\/a> to help core developers understand that need.<\/p>\n

<\/g><\/svg><\/a>FOCIL<\/h3>\n

While the headliner process encouraged the community to choose only one feature each for the execution and consensus layers for the sake of simplicity, Fork-choice enforced Inclusion Lists (FOCIL), which is a censorship-resistance feature, had exceptionally strong support and was moved to a conditional \u201cConsidered<\/a>\u201d status while the two chosen priorities were moved to \u201cScheduled<\/a>\u201d status. This was discussed<\/a> as being dependent on the progression of ePBS (the consensus layer feature and, to some extent, BALs (the execution layer feature) and also requires that FOCIL not significantly delay the upgrade.<\/p>\n

In this week\u2019s All Core Devs<\/a>, there was support for moving FOCIL to the upgrade that will follow Glamsterdam, Heka \/ Bogot\u00e1, conditional<\/a> on a yet-to-be-determined credible commitment for it to be in that upgrade. This decision will better inform developers on their availability to work on the smaller features, so they\u2019re not in limbo about whether or not they\u2019ll need to be scoping with FOCIL in mind.<\/p>\n

<\/g><\/svg><\/a>Timeline<\/h3>\n

There is not yet a proposed timeline for Glamsterdam beyond \u2018some time in 2026\u2019. It will depend on the total scope of the features chosen and the progress being made on the headliners. It\u2019s likely that the finalized set will be decided by the end of this year, then developers can focus on implementation and choosing the next upgrade\u2019s major features.<\/p>\n

It’s Devconnect week, which means that in-person conversations can accelerate consensus for next week’s All Core Devs Execution cal<\/a>l, but the next two Monday Testing calls are cancelled.<\/p>\n

<\/g><\/svg><\/a>Gas limit<\/h2>\n

All clients have confirmed readiness for 60 M by Fusaka. No action is needed by node operators beyond normal client updates before Fusaka – all clients will default to 60 M. Expect continued regular gas limit default increases now that there\u2019s an established framework<\/a> by Nethermind to think about safe limits to target. Node operators can still always signal their support for higher values by manually configuring<\/a> their limits.<\/p>\n

<\/g><\/svg><\/a>Heka \/ Bogot\u00e1 upgrade<\/h2>\n

With a now-established cadence of planning one fork while we implement the other, we can begin discussing the headline features for the Heka \/ Bogot\u00e1 upgrade after Fusaka is live. Heka was chosen<\/a> as the star name and the portmanteau<\/a> is still under discussion. After this week\u2019s All Core Devs call, we can expect FOCIL to be the frontrunner in the headliner selection process.<\/p>\n

Fusaka has been subject to the tension between two shipping priority strategies: ship safe or ship fast. The community has been pushing for faster forks and it shows in decision-making – Fusaka will ship 6 months and 26 days after Pectra, partially as a result of prioritizing speed more-so than in the past. Where dates in past forks have generally been chosen based on when all<\/em> clients are ready, Fusaka\u2019s timeline leaned more into dates when most<\/em> clients were ready.<\/p>\n

There was a unique edge to Fusaka\u2019s readiness in that its major features were originally part of Pectra before the upgrade was split into two, so their implementation had a head start, in a way. I don\u2019t expect to see the same timeliness in Glamsterdam though I do expect there to still be a push to ship as fast as possible.<\/p>\n

If this new structured process pioneered in the Glamsterdam upgrade does result in less chaos and stress, and more efficiency than Pectra had, it seems clear to me that the most gain is in long-term planning and defined structure for each step of the upgrade, rather than simply pushing developers to move faster, and we can then move to experiment with better parallelizing planning and development for future forks.<\/p>\n

If, however, Glamsterdam does still feel as overwhelming as Pectra initially did, we\u2019ll need to figure out how to more effectively rein in enthusiasm for adopting a wide set of features and a mindset of \u201cwe can do it all\u201d at the outset of an upgrade.<\/p>\n

For FOCIL being moved to Heka \/ Bogot\u00e1: it\u2019s tricky to definitively commit to a feature in an upgrade two forks in the future. We\u2019ve learned this in the past when a feature has been scheduled but the community moves on from their desire to implement it, and then it\u2019s an unfairly problematic process to have to remove it when developers are planning on it and have already begun work on it.<\/p>\n

If moved to the following upgrade, the best thing devs and the community can do for FOCIL is keep up active support for its prompt inclusion and not move on to a shiny new major feature that could diminish the understood urgency. Censorship resistance is critical for the fundamental value of Ethereum and it\u2019s important not to lose focus on that if some other exciting feature gains strong narrative.<\/p>\n

<\/g><\/svg><\/a>Relevant ACD calls:<\/h2>\n

[ October 2nd – November 13th ]<\/p>\n

ACDT: 61<\/a>, 60<\/a>, 59<\/a>, 58<\/a>, 57<\/a>, 56<\/a><\/p>\n

ACDC: 169<\/a>, 168<\/a>, 167<\/a>, 166<\/a><\/p>\n

ACDE: 224<\/a>, 223<\/a>, 222<\/a><\/p>\n

\"\"<\/p>\n<\/div>\n


\n
Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Ethereum\u2019s weekly All Core Developer calls are a lot to keep up with, so this “Checkpoint” series aims for high-level updates roughly every 4-6 weeks, depending on what\u2019s happening in core development. See the previous update here. If you enjoy reading core development updates, you may also be keen to learn that Forkcast now publishes […]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-17394","post","type-post","status-publish","format-standard","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17394","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=17394"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17394\/revisions"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=17394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=17394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=17394"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=17394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}