November 6, 2026
R&D

by Marius van der Wijden
Glamsterdam, the next update for Ethereum, is currently being tested on testnets. During these tests Chainsecurity has found a few projects that would be vulnerable after Glamsterdam since they rely on certain invariants. These invariants will be broken by EIP-8037 and EIP-8038 which rework how much gas is charged for certain operations and how gas is charged for state. You can learn more about the details of these potential issues on the Chainsecurity blog post or this tool. Based on these findings, ACD has decided to delay the hardfork process and not fork Hoodi until the issues are resolved. During this delay, the work on Hegota is not affected and is continuing in parallel in full force. In order to reach a pragmatic decision on the next
November 3, 2026
EcoDev

by Ethereum for Public Infrastructure and Commons team
Public services increasingly rely on digital systems that enable institutions to collaborate across organizational and national boundaries. Such cooperation may involve government agencies verifying documents issued by other authorities, or humanitarian organizations coordinating assistance while safeguarding sensitive personal information. Yet technical interoperability alone does not resolve a more fundamental question: who controls the infrastructure on which this cooperation depends? Ethereum offers a different foundation for digital public infrastructure. It is a global network that no single organization controls, and its software is open source for anyone to inspect, use, and build on. Our new website, https://publicsector.ethereum.foundation/, explores what these characteristics could mean for governments, multilateral organizations, NGOs, and other public-interest institutions. It brings together accessible explanations of Ethereum, case studies of real-world implementations, and practical resources for
October 22, 2026
Protocol

by Ethereum Foundation Protocol Cluster
The Glamsterdam upgrade on Hoodi, previously scheduled for October 26, 2026 at 17:42:48 UTC (epoch 132,352), has been postponed. A new activation date has not been set. This update supersedes the schedule and activation instructions in the Hoodi testnet announcement.
October 16, 2026
Protocol

by Ethereum Foundation Protocol Cluster
Update — October 22, 2026: The October 26 Hoodi activation has been postponed, including the scheduled gas-limit increase to 200M. The schedule and activation instructions below have been superseded. See Glamsterdam on Hoodi Postponed for details and operator guidance. Following its activation on Sepolia on October 6, the Glamsterdam network upgrade is now scheduled for the Hoodi testnet. Glamsterdam advances Ethereum's L1 scaling roadmap with enshrined proposer-builder separation, block-level access lists, and changes to gas pricing that better reflect the cost of execution and state growth. The Glamsterdam network upgrade is scheduled to activate on Hoodi at epoch 132,352, slot 4,235,264 (October 26, 2026, 17:42:48 UTC). At the same epoch, Hoodi's gas limit will be raised to 200M. See the activation table below for the deployment
October 5, 2026
R&D

by Ethereum Foundation Access Cluster
The Ethereum Foundation's Trillion Dollar Security initiative has identified blind signing and transaction uncertainty as a user experience risk, and is exploring native transaction assertions as a next step to enforce a transaction’s final outcome, alongside Clear Signing. This post covers why a valid signature doesn't always guarantee the transaction result you wanted, how native transaction assertions could protect users where today's defenses stop, and the design choices behind them, with EIP-7906 (Transaction Assertions via State Diff Opcode) as one possible approach.
October 1, 2026
R&D

by Vittorio Rivabella, dAI Team
tl;dr: zkAPI lets you pay for a metered API without being known. Deposit credits into an Ethereum vault once, then authorize bounded usage with zero-knowledge proofs instead of an identity. The provider sees the requests, and the payment layer sees the spend. Neither learns the link between them. The Open Anonymity Project built it with the Ethereum Foundation, and it runs on Ethereum Mainnet today.
September 28, 2026
Protocol

by Protocol
Glamsterdam follows the Fusaka upgrade, advancing Ethereum's L1 scaling roadmap with enshrined proposer-builder separation, block-level access lists, and changes to gas pricing that better reflect the cost of execution and state growth. The Glamsterdam network upgrade is scheduled to activate on Sepolia at epoch 353,024, slot 11,296,768 (October 6, 2026, 13:53:36 UTC). See the activation table below for the deployment schedule. Hoodi and mainnet activation dates have not yet been decided. Sepolia-compatible client versions will be added to the client release tables as they are confirmed. Node operators must update both their execution and consensus layer clients before activation.
September 9, 2026
R&D

by Ethereum Foundation Protocol Cluster
Every year since January 2019, teams from the Ethereum Foundation have spent an afternoon or two on r/ethereum answering questions from the community. The format hasn’t really changed: one thread, technical debates, detailed explanations, and community members asking whatever is on their mind. By now it is a tradition, and one of the more direct ways for the broader Ethereum community to hear from the people working on Ethereum's core development. The next session takes place on September 16th, with researchers and devs from the Protocol cluster answering your questions. The Glamsterdam hard fork is in public testing, the scope of Hegotá is being narrowed down, and the shape of the work beyond both upgrades is still being settled, so there is plenty to ask about. Questions might
September 7, 2026
R&D

by Ethereum Foundation Protocol Cluster
This is the EF Protocol cluster’s tier list for Hegotá. We evaluated the 62 EIPs proposed for inclusion, each with a tier and a short note on the grade. It is the first time the cluster has published one unified view rather than per-team opinions. Geth, of course, being an EL client will still ship their own standalone tier list. However, they and the rest of the Protocol cluster (about 60 people in total) across research and engineering worked together to include their feedback in this post as a datapoint along with that of every other team and individual contributor that decided to participate. The priorities that produced these grades are in the companion post, EF Protocol: Current and Emerging Priorities.

