As Ethereum’s 2026 roadmap becomes clearer, the developer community has reached a consensus on the year’s second major protocol update, named “Hegota.” Initially, the “Glamsterdam” update is expected to be implemented in the first half of 2026, with Hegota following in the second half. This planning signifies a shift towards more frequent protocol changes, underscoring Ethereum’s commitment to accelerating its technical evolution in response to increased network usage and scaling pressures.
Hegota Accelerates Ethereum’s Development Schedule
Ethereum’s developers are moving away from the practice of a single major annual update, aiming for two significant updates in 2026. Following the first phase, Glamsterdam, the planned Hegota provides a model of faster and incremental technical progress for the network. Core developers aspire to manage risks more effectively and respond swiftly to user demands through smaller yet more frequent updates.
This strategy is rooted in criticisms from earlier in the year within the Ethereum community. Some developers and application founders asserted that protocol developments were lagging behind network growth. The new roadmap reflects a restructuring of developer coordination and shorter delivery times following these critiques.
Clarifying the scope for Hegota will take time, with developer meetings currently prioritizing the completion of Glamsterdam’s content. Consequently, Ethereum Improvement Proposals for Hegota are expected to be announced no earlier than February. Nevertheless, early-stage discussions are already underway on technical topics.
What to Expect with the Hegota Update?
One of the prominent technical aspects of the Hegota update is the incorporation of Verkle Trees, a data structure aimed at allowing nodes to store and verify large data sets more efficiently. Reduced hardware requirements will make running nodes more accessible to individual participants, thereby enhancing decentralization.
Previous updates in the altcoin network have seen certain proposals deferred due to time or complexity constraints. It is anticipated that the same approach will apply to the Hegota process, potentially bringing postponed technical work from Glamsterdam into the spotlight during the year’s second update.
Naming tradition continues as Hegota combines the execution layer “Bogota” with the consensus layer “Heze.” The Ethereum Foundation’s recent blog post recapped key innovations like PeerDAS from the Fusaka update and planned features like block-level access lists and Proposer-Builder Separation for Glamsterdam. Attention now turns towards the developing technical framework of the Hegota phase.
