{"id":"hegota-upgrade","hidden":false,"ipfs":"QmRZwtq85jhwZkGJeSfpU5av4mZMLngfQ7czVrESTwWmAf","language":"en","transactionHash":"0xe0754e502bba4af47e2b8aa69624dc6037432406589f9f1d62b4e95267ddd4ca","created":"2026-01-26T00:24:14.539Z","updated":"2026-01-26T00:24:14.539Z","title":"Ethereum Hegota Upgrade","summary":"Hegota is a planned Ethereum network upgrade that will follow the Glamsterdam hard fork and is tentatively targeted for mainnet in Q2 2027.","content":"**Hegota** is a planned major network upgrade, or [hard fork](https://iq.wiki/wiki/hard-fork), for the [Ethereum](https://iq.wiki/wiki/ethereum) [blockchain](https://iq.wiki/wiki/blockchain) that is expected on [mainnet](https://iq.wiki/wiki/mainnet) in Q2 2027, with the precise activation date not yet confirmed.[[8]](#cite-id-5vhosfpqjn) As the designated successor to the [Glamsterdam](https://iq.wiki/wiki/ethereum-glamsterdam-upgrade) upgrade, Hegota represents a key part of [Ethereum](https://iq.wiki/wiki/ethereum)'s accelerated development roadmap, which prioritizes more frequent and incremental protocol updates. The upgrade's primary objectives are to advance [Ethereum](https://iq.wiki/wiki/ethereum)'s scalability, improve network decentralization by lowering barriers to entry for [node](https://iq.wiki/wiki/node) operators, and address the long-term challenge of state size growth. While much of the scope beyond two EIPs already scheduled for inclusion is still being defined, with dozens of additional EIPs under active discussion, long-term roadmap discussions associated with Hegota emphasize Verkle trees and state and history expiry as important directions for addressing state growth rather than as confirmed headline features of this specific upgrade.[[8]](#cite-id-5vhosfpqjn)[[9]](#cite-id-9tfk2pns68)[[11]](#cite-id-a8pjobou1q)[[1]](#cite-id-C9wFfvx7LDMP2Yrn)[[2]](#cite-id-3lNe0iTsPRG8C2iN)[[3]](#cite-id-zQAHUrzLpJp6m0z5)​\n\n## Background and Roadmap\nThe Hegota upgrade is a product of a strategic shift in [Ethereum](https://iq.wiki/wiki/ethereum)'s core development philosophy that emerged in 2025. This new approach favors a faster cadence of network upgrades, aiming for approximately two [hard forks](https://iq.wiki/wiki/hard-fork) per year. This strategy was adopted in part as a response to criticism from some community members and builders in early 2025 who argued that the pace of protocol development was too slow to meet the network's growing demands. By shipping smaller, more focused updates more frequently, developers aim to introduce improvements in a more predictable and manageable manner, rather than bundling numerous complex changes into large, less frequent releases.[[1]](#cite-id-C9wFfvx7LDMP2Yrn)[[4]](#cite-id-eFPljHwOV1RsY53j)​\n\nHegota follows a series of upgrades designed to enhance [Ethereum](https://iq.wiki/wiki/ethereum)'s capabilities. It comes after the [Fusaka upgrade](https://iq.wiki/wiki/fusaka), which successfully implemented [PeerDAS](https://iq.wiki/wiki/eip-7594-peerdas), and the [Glamsterdam upgrade](https://iq.wiki/wiki/ethereum-glamsterdam-upgrade), which is planned for the first half of 2026. The major features slated for Glamsterdam include Block-level Access Lists and enshrined Proposer-Builder Separation (ePBS). In line with the biannual cadence, Glamsterdam remains the preceding upgrade, but [Ethereum](https://iq.wiki/wiki/ethereum).org now lists Hegota's [mainnet](https://iq.wiki/wiki/mainnet) target as Q2 2027, with the exact date yet to be confirmed.[[5]](#cite-id-FEKWxQ2L94h2dU4R)[[4]](#cite-id-eFPljHwOV1RsY53j)[[8]](#cite-id-5vhosfpqjn)​\n\nIn a December 22, 2025 blog post, the [Ethereum Foundation](https://iq.wiki/wiki/ethereum-foundation-ef) contextualized the roadmap leading to Hegota:\n\n> “Fusaka shipped PeerDAS in addition to a myriad of minor features and Glamsterdam’s major features will include Block-level Access Lists and enshrined Proposer-Builder Separation. Now we begin outlining the subsequent upgrade: Hegota.”[[5]](#cite-id-FEKWxQ2L94h2dU4R)[[1]](#cite-id-C9wFfvx7LDMP2Yrn)\n\n## Naming Convention\n\nThe name \"Hegota\" continues the established naming convention for [Ethereum](https://iq.wiki/wiki/ethereum) network upgrades, which combines a name for the Execution Layer (EL) update with a name for the Consensus Layer (CL) update. The name was officially agreed upon by core developers during the final All Core Developers Execution (ACDE) call of 2025.[[6]](#cite-id-By1uCpvUXbzMLPag)\n\nThe components of the name are:\n\n* **Bogota:** The name for the Execution Layer upgrade, chosen in honor of Bogotá, Colombia, the host city for the [Devcon](https://iq.wiki/wiki/devcon) VI developer conference.[[1]](#cite-id-C9wFfvx7LDMP2Yrn)[[4]](#cite-id-eFPljHwOV1RsY53j)\n* **Heze:** The name for the Consensus Layer upgrade, named after a star.[[1]](#cite-id-C9wFfvx7LDMP2Yrn)[[6]](#cite-id-By1uCpvUXbzMLPag)\n\nThe two names are merged to create the portmanteau **Hegota** (**He**ze + Bo**gota**) for the combined network [hard fork](https://iq.wiki/wiki/hard-fork).[[1]](#cite-id-C9wFfvx7LDMP2Yrn)\n\n## Development and Scoping Process\n\nThe process for determining the contents of the Hegota upgrade is coordinated through a meta [Ethereum](https://iq.wiki/wiki/ethereum) Improvement Proposal, EIP-8081. This EIP does not introduce any protocol changes itself but serves as a central tracking issue and master list for all EIPs being considered for or scheduled for inclusion in the [hard fork](https://iq.wiki/wiki/hard-fork).[[7]](#cite-id-GOpi1SoxbCmRomUE)[[2]](#cite-id-3lNe0iTsPRG8C2iN)​\n\nOn December 3, 2025, [Ethereum](https://iq.wiki/wiki/ethereum) [Foundation](https://iq.wiki/wiki/foundation) researcher Alex Stokes proposed a formal scoping process on the Fellowship of [Ethereum](https://iq.wiki/wiki/ethereum) Magicians forum. This structured approach was designed to provide clarity and incorporate lessons from previous upgrades. The process aims to define a clear \"[fork](https://iq.wiki/wiki/fork) focus\" by prioritizing the selection of one or more major features before considering smaller additions. Community member Andrew Coathup suggested potential focus areas could include [Layer 1](https://iq.wiki/wiki/layer-1) or [Layer 2](https://iq.wiki/wiki/layer-2) scaling, user experience (UX), developer experience (DX), or decentralization.[[7]](#cite-id-GOpi1SoxbCmRomUE)​\n\n### Headliner and Non-Headliner EIPs\n\nThe selection process distinguishes between two categories of proposals:\n\n* **Headliners:** These are the major, defining features of the upgrade that address its primary objective. Champions of headliner EIPs must submit their proposals on the [Ethereum](https://iq.wiki/wiki/ethereum) Magicians forum using a specific template. This template requires a plain-language summary, detailed justification, analysis of stakeholder impacts, and an assessment of technical readiness and security risks.[[7]](#cite-id-GOpi1SoxbCmRomUE)\n* **Non-Headliners:** These are smaller improvements or minor features. A submission window for non-headliner EIPs opens for 30 days only after the headliner features have been finalized by the All Core Developers. A rule was also established stating that an EIP proposed as a headliner but not selected cannot be re-proposed as a non-headliner for the same upgrade.[[5]](#cite-id-FEKWxQ2L94h2dU4R)[[7]](#cite-id-GOpi1SoxbCmRomUE)\n\n### Scoping Timeline\n\nThe timeline for defining Hegota's scope was formally announced in late 2025. Given the current date of January 26, 2026, the process is actively underway.[[5]](#cite-id-FEKWxQ2L94h2dU4R)​\n\n* **December 3, 2025:** [Ethereum Foundation](https://iq.wiki/wiki/ethereum-foundation-ef) researcher Alex Stokes posted the proposed scoping timeline on the [Ethereum](https://iq.wiki/wiki/ethereum) Magicians forum.\n* **December 22, 2025:** The [Ethereum](https://iq.wiki/wiki/ethereum) [Foundation](https://iq.wiki/wiki/foundation)'s Protocol Support team published a blog post formally outlining the timeline for the Hegota upgrade's proposal and selection process.\n* **January 8 – February 4, 2026:** The submission window for \"headliner\" EIP proposals is open. To be considered, proposals must be submitted to the [Ethereum](https://iq.wiki/wiki/ethereum) Magicians forum and presented during an All Core Devs call within this period.\n* **February 5 – February 26, 2026:** A period is scheduled for All Core Devs teams to discuss, evaluate, and finalize the headliner feature(s) for the upgrade.\n* **Post-February 26, 2026:** Following the selection of the headliner(s), a 30-day window will open for the submission of \"non-headliner\" EIP proposals.\n\nThe timeline for discussion and finalization is subject to change based on the progress of developer consensus.[[5]](#cite-id-FEKWxQ2L94h2dU4R)[[7]](#cite-id-GOpi1SoxbCmRomUE)​\n\n## Goals and Potential Features\nThe primary goals of the Hegota upgrade are to enhance [Ethereum](https://iq.wiki/wiki/ethereum)'s scalability, strengthen its decentralization, and implement a long-term solution for managing the growth of [blockchain](https://iq.wiki/wiki/blockchain) state, often referred to as \"state bloat.\" Discussions among core developers and the community have highlighted several key proposals and areas of interest aligned with these aims, and as of October 2026 two EIPs—FOCIL and frame transactions—are formally scheduled for inclusion, while the remainder of the scope is still being decided.[[3]](#cite-id-zQAHUrzLpJp6m0z5)[[4]](#cite-id-eFPljHwOV1RsY53j)[[9]](#cite-id-9tfk2pns68)[[8]](#cite-id-5vhosfpqjn) Core developers are evaluating a broad set of around 60–70 EIPs for possible inclusion, covering areas such as privacy, censorship resistance, performance improvements, and preparation for post-quantum cryptography, with only a subset expected to meet the timeline and readiness requirements for the upgrade.[[8]](#cite-id-5vhosfpqjn)[[11]](#cite-id-a8pjobou1q)\n\n### Scheduled Headliner EIPs\nAccording to EIP-8081 and the [Ethereum](https://iq.wiki/wiki/ethereum).org roadmap, two EIPs are scheduled for inclusion in Hegota. EIP-7805, Fork-choice enforced inclusion lists (FOCIL), is the confirmed headliner and is focused on censorship resistance by requiring [block](https://iq.wiki/wiki/block) builders to honor transaction inclusion lists proposed by [validator](https://iq.wiki/wiki/validator) committees, helping ensure that valid transactions cannot be indefinitely excluded by individual builders.[[9]](#cite-id-9tfk2pns68)[[8]](#cite-id-5vhosfpqjn) Under the FOCIL design, [validator](https://iq.wiki/wiki/validator) committees publish inclusion lists that [block](https://iq.wiki/wiki/block) builders are obligated to incorporate when constructing [blocks](https://iq.wiki/wiki/block), reducing the ability of any single builder to censor specific transactions.[[8]](#cite-id-5vhosfpqjn)[[11]](#cite-id-a8pjobou1q) [Ethereum](https://iq.wiki/wiki/ethereum) co-founder [Vitalik Buterin](https://iq.wiki/wiki/vitalik-buterin) has publicly supported FOCIL and described it as part of a broader roadmap toward a more censorship-resistant \"world computer,\" while some developers and community members have raised concerns that requiring the inclusion of all valid transactions could heighten legal or regulatory risks for [validators](https://iq.wiki/wiki/validator) if those transactions involve sanctioned addresses.[[12]](#cite-id-qr9ji9mtaa)[[13]](#cite-id-q4w1isfest) EIP-8141, Frame transactions, is listed as scheduled on the roadmap and introduces a transaction model that lets accounts define their own validation logic, enabling native account abstraction, more flexible authentication schemes, and features such as social recovery or multi-approval wallets without relying on extra off-protocol infrastructure.[[9]](#cite-id-9tfk2pns68)[[8]](#cite-id-5vhosfpqjn)[[11]](#cite-id-a8pjobou1q) Frame transactions are designed to support advanced wallet behaviors such as fee sponsorship, bundling several actions into a single transaction, and using alternative signature schemes, and are particularly relevant for privacy-focused applications that currently depend on external relayers and other off-chain services to submit transactions on users' behalf.[[8]](#cite-id-5vhosfpqjn)[[11]](#cite-id-a8pjobou1q) While frame transactions are being tracked as part of Hegota's planned scope, core developers have indicated that, unlike FOCIL, they remain under evaluation alongside many other proposals and could still be modified or deferred based on testing and implementation constraints.[[11]](#cite-id-a8pjobou1q)\n\n### Verkle Trees\nVerkle trees are a major long-term roadmap item for [Ethereum](https://iq.wiki/wiki/ethereum) that is frequently discussed in connection with Hegota but has not been formally scheduled as a headliner for the upgrade. Verkle trees are a novel data structure that is significantly more efficient for producing proofs of data than the Merkle Patricia trees currently used by [Ethereum](https://iq.wiki/wiki/ethereum). Their implementation would allow [Ethereum](https://iq.wiki/wiki/ethereum) [nodes](https://iq.wiki/wiki/node) to store and mathematically verify large amounts of state data using much smaller \"proofs.\"[[1]](#cite-id-C9wFfvx7LDMP2Yrn)[[4]](#cite-id-eFPljHwOV1RsY53j)\n\nThe main benefits of implementing Verkle trees are:\n\n* **Reduced Hardware Requirements:** They would dramatically lower the hardware requirements, especially disk space, needed to operate a full [node](https://iq.wiki/wiki/node). This is a crucial step toward enabling \"stateless clients,\" which can verify the chain without storing the entire state.[[3]](#cite-id-zQAHUrzLpJp6m0z5)[[4]](#cite-id-eFPljHwOV1RsY53j)\n* **Improved Decentralization:** By making it cheaper and easier for more individuals to run full [nodes](https://iq.wiki/wiki/node), Verkle trees aim to enhance the network's decentralization, resilience, and security.[[1]](#cite-id-C9wFfvx7LDMP2Yrn)\n\n### State and History Management\nAnother major long-term roadmap area discussed alongside Hegota is the implementation of mechanisms for state and history expiration. This concept involves allowing older, less frequently accessed state and historical data on the [blockchain](https://iq.wiki/wiki/blockchain) to be pruned from the active set that full [nodes](https://iq.wiki/wiki/node) must maintain. This directly addresses the problem of state bloat, which poses a long-term challenge to scalability by making it increasingly difficult for new [nodes](https://iq.wiki/wiki/node) to join and sync with the network.[[3]](#cite-id-zQAHUrzLpJp6m0z5)[[10]](#cite-id-2c41g2pek4)[[4]](#cite-id-eFPljHwOV1RsY53j)\n\n### Other Potential Inclusions\nSeveral other EIPs and concepts are considered potential candidates for the Hegota upgrade, many of which may be deferred from the preceding Glamsterdam upgrade if they are not ready in time.[[1]](#cite-id-C9wFfvx7LDMP2Yrn)\n\n* **Enshrined Proposer-Builder Separation (ePBS):** This is a protocol-level change to formalize the separation of roles between [block](https://iq.wiki/wiki/block) proposers ([validators](https://iq.wiki/wiki/validator) who select [blocks](https://iq.wiki/wiki/block)) and [block](https://iq.wiki/wiki/block) builders (sophisticated entities that construct blocks). The goal is to mitigate centralization risks by preventing a concentration of power among a few large block builders. While ePBS is a major feature of Glamsterdam, any complexities could push its implementation to Hegota.[[3]](#cite-id-zQAHUrzLpJp6m0z5)[[4]](#cite-id-eFPljHwOV1RsY53j)\n* **FOCIL:** Fork-choice enforced inclusion lists (FOCIL, EIP-7805) is now listed among the \"EIPs Scheduled for Inclusion\" in the Hegota Meta EIP and is treated as the headliner for the upgrade, with a primary focus on improving censorship resistance.[[5]](#cite-id-FEKWxQ2L94h2dU4R)[[9]](#cite-id-9tfk2pns68)\n* **Execution Layer Optimizations:** General improvements to the efficiency of the [Ethereum](https://iq.wiki/wiki/ethereum) Virtual Machine (EVM) and other aspects of the execution layer are often included in network upgrades and may be part of Hegota. This could include adjustments to [gas](https://iq.wiki/wiki/gas) costs for various operations.[[10]](#cite-id-2c41g2pek4)[[4]](#cite-id-eFPljHwOV1RsY53j)\n\nAmong earlier ideas discussed for Hegota was EIP-8363, the \"Tapered Issuance Burn\" proposal, which suggested burning an increasing share of [staking](https://iq.wiki/wiki/staking) rewards as more [ETH](https://iq.wiki/wiki/ether) is staked, up to 100% of [validator](https://iq.wiki/wiki/validator) rewards at around 60.25 million staked ETH.[[14]](#cite-id-hwjlud9kdc)[[13]](#cite-id-q4w1isfest) The proposal generated extensive discussion and attracted criticism from some [DeFi](https://iq.wiki/wiki/decentralized-finance-defi) projects and other stakeholders concerned about its impact on staking economics before its authors formally withdrew it from the Hegota scoping process in October 2026, following feedback that [ETH](https://iq.wiki/wiki/ether) issuance policy should be handled through a separate, dedicated process rather than as part of a single network upgrade.[[14]](#cite-id-hwjlud9kdc)[[15]](#cite-id-gje9nbbb4j) Its authors have indicated that issuance will instead be discussed on a standalone track, with community debate expected to extend through [Devcon](https://iq.wiki/wiki/devcon) and EthCC 2026, and EIP-8363 is no longer part of Hegota’s scoped feature set.[[15]](#cite-id-gje9nbbb4j)[[14]](#cite-id-hwjlud9kdc)","recentActivity":null,"operator":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"categories":[{"id":"glossary","title":"glossary"}],"tags":[],"images":[{"id":"QmdpCJcav1PpHaeEoua8FdukqGA6cmrp1N9QuXRo84RPst","type":"image/jpeg, image/png"}],"media":[],"linkedWikis":{"founders":[],"blockchains":["ethereum"],"speakers":[]},"events":[],"founderWikis":[],"blockchainWikis":[{"id":"ethereum","title":"Ethereum"}],"metadata":[{"id":"wiki-score","value":"71"},{"id":"references","value":"[{\"id\":\"C9wFfvx7LDMP2Yrn\",\"url\":\"https://www.coindesk.com/tech/2025/12/28/ethereum-s-hegota-upgrade-slated-for-late-2026-as-devs-accelerate-roadmap\",\"description\":\"CoinDesk on Hegota as a major 2026 upgrade\",\"timestamp\":1769386385956},{\"id\":\"3lNe0iTsPRG8C2iN\",\"url\":\"https://www.theblock.co/post/383275/ethereum-developers-name-post-glamsterdam-upgrade-hegota-as-2026-roadmap-takes-shape\",\"description\":\"The Block reports on Hegota following Glamsterdam\",\"timestamp\":1769386385956},{\"id\":\"zQAHUrzLpJp6m0z5\",\"url\":\"https://www.onesafe.io/blog/ethereum-hegota-upgrade-scaling-crypto-solutions\",\"description\":\"OneSafe on Hegota's goals of scalability and decentralization\",\"timestamp\":1769386385956},{\"id\":\"eFPljHwOV1RsY53j\",\"url\":\"https://forklog.com/en/ethereums-hegota-hard-fork-scheduled-for-late-2026/\",\"description\":\"Forklog on the shift to a biannual release cycle\",\"timestamp\":1769386385956},{\"id\":\"FEKWxQ2L94h2dU4R\",\"url\":\"https://blog.ethereum.org/2025/12/22/hegota-timeline\",\"description\":\"Ethereum Foundation blog on the upgrade sequence\",\"timestamp\":1769386385956},{\"id\":\"By1uCpvUXbzMLPag\",\"url\":\"https://www.bankless.com/read/news/ethereum-core-devs-pin-hegota-upgrade-on-2026-roadmap\",\"description\":\"Bankless on the Hegota naming convention and ACDE decision\",\"timestamp\":1769386385956},{\"id\":\"GOpi1SoxbCmRomUE\",\"url\":\"https://ethereum-magicians.org/t/eip-8081-hegota-network-upgrade-meta-thread/26876\",\"description\":\"Ethereum Magicians meta thread for EIP-8081\",\"timestamp\":1769386385956},{\"id\":\"5vhosfpqjn\",\"url\":\"https://ethereum.org/roadmap/hegota/\",\"description\":\"Ethereum.org Hegotá roadmap overview\",\"timestamp\":1791390322005},{\"id\":\"9tfk2pns68\",\"url\":\"https://eips.ethereum.org/EIPS/eip-8081\",\"description\":\"EIP-8081 meta EIP for Hegotá\",\"timestamp\":1791390322005},{\"id\":\"2c41g2pek4\",\"url\":\"https://www.bankless.com/read/news/ethereum-core-devs-pin-hegota-upgrade-hegota-as-2026-roadmap-takes-shape\",\"description\":\"Bankless on the Hegota naming convention and ACDE decision\",\"timestamp\":1791390322005},{\"id\":\"a8pjobou1q\",\"url\":\"https://www.coindesk.com/tech/2026/08/17/ethereum-s-next-big-upgrade-has-66-proposals-including-a-major-privacy-fix\",\"description\":\"CoinDesk on 66 Hegotá proposals and privacy focus\",\"timestamp\":1791390439609},{\"id\":\"qr9ji9mtaa\",\"url\":\"https://coinmarketcap.com/academy/article/vitalik-buterin-backs-focil-as-ethereum-schedules-hegota-upgrade\",\"description\":\"CoinMarketCap on Vitalik Buterin's support for FOCIL\",\"timestamp\":1791391330392},{\"id\":\"q4w1isfest\",\"url\":\"https://finance.biggo.com/news/bb0d6d89-d1b9-45cf-b901-1d3631f267df\",\"description\":\"BigGo Finance on FOCIL debate\",\"timestamp\":1791391330392},{\"id\":\"hwjlud9kdc\",\"url\":\"https://www.theblock.co/news/ecosystems/2026-10-01-ethereum-staking-reward-burn-proposal-eip-8363-pulled-hegota-upgrade-417419\",\"description\":\"The Block on EIP-8363 withdrawal from Hegota\",\"timestamp\":1791391330392},{\"id\":\"gje9nbbb4j\",\"url\":\"https://unchainedcrypto.com/authors-withdraw-ethereum-staking-reward-burn-plan-from-hegota-upgrade-seek-separate-process/\",\"description\":\"Unchained on authors withdrawing EIP-8363 from Hegota\",\"timestamp\":1791391330392}]"},{"id":"previous_cid","value":"QmUcfE3TWn35mC9uQAsCMo3TCqVwcvbAk5m2ZCBxNsQxTk"},{"id":"commit-message","value":"Expand Ethereum Hegota Upgrade wiki by 188 words"},{"id":"previous_cid","value":"QmUcfE3TWn35mC9uQAsCMo3TCqVwcvbAk5m2ZCBxNsQxTk"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"views":301}