{"id":"ethereum-glamsterdam-upgrade","hidden":false,"ipfs":"QmWQ2g8aarAxsMdV5QcyH6ChghpbhLanqS9DzmbHhQGstt","language":"en","transactionHash":"0x82f828cc1986befad7133242feca2062bde87e51d75fb284b0b79039dfa1097a","created":"2025-07-29T20:33:15.867Z","updated":"2026-10-24T14:37:09.573Z","title":"Ethereum Glamsterdam Upgrade","summary":"Glamsterdam is Ethereum’s planned next major upgrade, focused on L1 and blob scaling. Sepolia has activated it; Hoodi testing is postponed, and mainnet has no confirmed date.","content":"**Glamsterdam** is [Ethereum](https://iq.wiki/wiki/ethereum)’s planned next major upgrade after Fusaka, intended to scale the [Layer 1](https://iq.wiki/wiki/layer-1) and blob throughput.[[10]](#cite-id-r0wljdgupo) Sepolia activated the upgrade on October 6, 2026; Hoodi’s planned October 26 activation was postponed on October 22, and no replacement Hoodi date had been announced by November 3. The [Ethereum](https://iq.wiki/wiki/ethereum) roadmap still gives Q4 2026 as the expected [mainnet](https://iq.wiki/wiki/mainnet) quarter but confirms no mainnet date. Sepolia’s activation did not mean Glamsterdam activated on mainnet, and the Hoodi postponement did not set a mainnet date.[[16]](#cite-id-dgvlv156ef)[[20]](#cite-id-gmww6tirvn)[[21]](#cite-id-k9edahsd40)\n\n## Overview\nGlamsterdam represents a crucial phase in [Ethereum](https://iq.wiki/wiki/ethereum)'s ongoing evolution, aiming to address persistent challenges such as network scalability and high [transaction fees](https://iq.wiki/wiki/transaction-fee). Planned as the successor to the [Fusaka](https://iq.wiki/wiki/fusaka) upgrade, it is expected on [mainnet](https://iq.wiki/wiki/mainnet) in Q4 2026, with the exact date not yet confirmed; this target is not a fixed or scheduled [mainnet](https://iq.wiki/wiki/mainnet) date, and as of November 3, 2026, no specific [mainnet](https://iq.wiki/wiki/mainnet) epoch or timestamp has been set.[[21]](#cite-id-k9edahsd40) The [Ethereum Foundation](https://iq.wiki/wiki/ethereum-foundation-ef) has reorganized its research and development division into \"Protocol,\" a leaner and more focused entity led by veterans like [Tim Beiko](https://iq.wiki/wiki/tim-beiko) and [Ansgar Dietrichs](https://iq.wiki/wiki/ansgar-dietrichs). This reorganization prioritizes scaling the [Layer 1](https://iq.wiki/wiki/layer-1) (L1), expanding blobspace, and improving user experience (UX), mandates that directly align with the expected priorities of Glamsterdam.[[2]](#cite-id-LOWNMso5Cb)\n\n $$widget0 [YOUTUBE@VID](https://youtube.com/watch?v=Hfz4xubm6kc)$$ \n\nThe development approach for Glamsterdam emphasizes stability and thorough testing, reflecting the iterative nature of [blockchain](https://iq.wiki/wiki/blockchain) development. By September 2026, the upgrade had passed through several dedicated private devnets and, under Meta‑EIP‑7773, the Sepolia [testnet](https://iq.wiki/wiki/testnet) [fork](https://iq.wiki/wiki/fork) was assigned a fixed activation at epoch 353,024, slot 11,296,768 (October 6, 2026, 13:53:36 UTC), while activation parameters for the Hoodi [testnet](https://iq.wiki/wiki/testnet) and [mainnet](https://iq.wiki/wiki/mainnet) remained unscheduled.[[16]](#cite-id-dgvlv156ef)[[21]](#cite-id-k9edahsd40) The Sepolia upgrade activated and finalized successfully on that schedule, serving as a major public rehearsal of Glamsterdam’s scope, but did not itself define Hoodi or [mainnet](https://iq.wiki/wiki/mainnet) activation dates.[[18]](#cite-id-sgo1al59yl)[[19]](#cite-id-ox1v5bhc61) On October 22, 2026, core developers postponed the Hoodi activation that had been planned for October 26; no replacement date had been announced by November 3. The roadmap continued to list Q4 2026 as the expected [mainnet](https://iq.wiki/wiki/mainnet) quarter without confirming a mainnet date. Sepolia activation and the Hoodi postponement did not set a mainnet activation date.[[20]](#cite-id-gmww6tirvn)[[21]](#cite-id-k9edahsd40) In advance of the Sepolia [fork](https://iq.wiki/wiki/fork), [node](https://iq.wiki/wiki/node) operators were required to update both their execution and consensus clients to Sepolia‑compatible releases.[[16]](#cite-id-dgvlv156ef) This commitment to staged testing is intended to ensure that new features are robust and well-integrated into the network's broader roadmap. The successful implementation of Glamsterdam is expected to significantly impact the entire [Ethereum](https://iq.wiki/wiki/ethereum) ecosystem, benefiting investors through enhanced network efficiency, developers through new functionalities and tools, and users through a more [stable](https://iq.wiki/wiki/stable), secure, and cost-effective experience.[[2]](#cite-id-LOWNMso5Cb)[[3]](#cite-id-rfAZoUE0K3)\n\n## Naming Convention\n\n[Ethereum](https://iq.wiki/wiki/ethereum) network upgrades traditionally derive their names from various sources, often combining a star name for the Consensus Layer (CL) upgrade with a city name for the Execution Layer (EL) upgrade. Historically, [Devcon](https://iq.wiki/wiki/devcon) cities were used for naming upgrades. However, with [Devcon](https://iq.wiki/wiki/devcon) becoming a biennial event, the use of Devconnect city names, such as Amsterdam, has been adopted for annual upgrades. For Glamsterdam, the name combines \"Gloas,\" a G-star, with \"Amsterdam,\" the city that hosted a recent Devconnect event. This naming convention is part of a Meta [Ethereum](https://iq.wiki/wiki/ethereum) Improvement Proposal (EIP-7773: [Hardfork](https://iq.wiki/wiki/hard-fork) Meta - Amsterdam).[[1]](#cite-id-3imVvYHRKv)\n\n## Development Roadmap\nThe Glamsterdam upgrade is positioned as the successor to the [Fusaka](https://iq.wiki/wiki/fusaka) upgrade. Earlier planning in 2025 tentatively placed Fusaka’s [mainnet](https://iq.wiki/wiki/mainnet) deployment in early November 2025; that was a historical forecast, not a current forecast for Glamsterdam.[[4]](#cite-id-1otWM0BVGC)[[5]](#cite-id-lbk79tETJu) [Ethereum](https://iq.wiki/wiki/ethereum) core developers have outlined a detailed roadmap for Glamsterdam, encompassing several critical phases from feature selection to [mainnet](https://iq.wiki/wiki/mainnet) activation. This structured approach aims to ensure a smooth and secure transition for the network.\n\n### Headliner Selection Phase\n\nThe initial phase involved the selection of \"headliner\" features to define Glamsterdam's primary focus. During the All Core Developers Consensus Call #162, [Ethereum](https://iq.wiki/wiki/ethereum) core developers officially selected EIP-7732, also known as enshrined Proposer-Builder Separation (ePBS), as the consensus layer headliner for the upgrade. This decision finalized the thematic direction of the upgrade, prioritizing protocol-level decentralization and censorship resistance over other candidates.[[4]](#cite-id-1otWM0BVGC)[[7]](#cite-id-ARj8e3zdv9)\n\n### Proposal Deadline and Specification Freeze\n\nTo prevent scope creep and ensure timely progress, a strict deadline was set for finalizing headliner choices and submitting regular [EIPs](https://iq.wiki/wiki/ethereum-improvement-proposal-eip). This cut-off, set for August 21, 2025, allowed developers to merge, audit, and document all included EIPs before the network enters the rigorous testing phase. This disciplined approach is crucial for managing the complexity of a major [blockchain](https://iq.wiki/wiki/blockchain) upgrade. However, some developers have raised concerns that the intense focus on planning for Glamsterdam, which is not expected until 2026, might be diverting attention and resources from the upcoming Fusaka upgrade, potentially putting its Q4 2025 timeline at risk.[[4]](#cite-id-1otWM0BVGC)[[8]](#cite-id-jRI3wv4V9g)\n\n### Testing and Audit Windows\nThe rollout process for Glamsterdam begins with the creation of dedicated client release branches that track the frozen specifications, followed by a sequence of private and public [testnets](https://iq.wiki/wiki/testnet). By September 2026, [Ethereum](https://iq.wiki/wiki/ethereum) client teams had iterated through multiple private devnets, culminating in a full dress rehearsal on Devnet-11 designed to exercise enshrined Proposer-Builder Separation (ePBS), block-level parallel execution, and state-cost repricing under stressed conditions.[[11]](#cite-id-a9o6skjpa2)[[12]](#cite-id-i53b1rvqsn)\n\nOn September 17, 2026, the [Ethereum Foundation](https://iq.wiki/wiki/ethereum-foundation-ef) announced that the Glamsterdam upgrade was scheduled to activate on the Sepolia [testnet](https://iq.wiki/wiki/testnet) at epoch 353,024, slot 11,296,768, corresponding to October 6, 2026, 13:53:36 UTC, as specified in Meta‑EIP‑7773.[[16]](#cite-id-dgvlv156ef) The Sepolia [fork](https://iq.wiki/wiki/fork) occurred as planned, finalized successfully, and raised Sepolia’s target [gas](https://iq.wiki/wiki/gas) limit from roughly 60 million to around 200 million [gas](https://iq.wiki/wiki/gas) per [block](https://iq.wiki/wiki/block) as a capacity stress test for Glamsterdam’s new mechanisms.[[17]](#cite-id-beh4cp90n1)[[18]](#cite-id-sgo1al59yl)[[19]](#cite-id-ox1v5bhc61) These public [testnets](https://iq.wiki/wiki/testnet) are vital for identifying interoperability issues under realistic network conditions and for broader community participation, allowing [dApp](https://iq.wiki/wiki/decentralized-application) developers, [node](https://iq.wiki/wiki/node) operators, and researchers to test their applications and infrastructure against the new changes. [Ethereum](https://iq.wiki/wiki/ethereum).org and roadmap updates describe Glamsterdam as expected in Q4 2026 on [mainnet](https://iq.wiki/wiki/mainnet), but as of November 3, 2026, no specific [mainnet](https://iq.wiki/wiki/mainnet) date or epoch has been confirmed; the target remains subject to change based on [testnet](https://iq.wiki/wiki/testnet) outcomes. Sepolia’s successful activation was a [testnet](https://iq.wiki/wiki/testnet) milestone, not [mainnet](https://iq.wiki/wiki/mainnet) activation. The postponement of Hoodi testing likewise did not set a mainnet date.[[21]](#cite-id-k9edahsd40)[[20]](#cite-id-gmww6tirvn)\n\n### Hoodi Testnet Postponement\nAt ACDE #248, core developers postponed the Hoodi Glamsterdam activation scheduled for October 26, 2026, to allow further review of how [EIP-8037](https://iq.wiki/wiki/eip-8037)’s state-creation [gas](https://iq.wiki/wiki/gas) accounting interacts with [smart contracts](https://iq.wiki/wiki/smart-contract) deployed on [mainnet](https://iq.wiki/wiki/mainnet).[[20]](#cite-id-gmww6tirvn) The previously planned activation at 17:42:48 UTC, epoch 132,352, was removed, as was the simultaneous Hoodi gas-limit schedule that would have raised the limit to 200 million.[[20]](#cite-id-gmww6tirvn) No replacement epoch or timestamp had been announced by November 3, 2026.[[20]](#cite-id-gmww6tirvn)\n\nThe change removes the future-upgrade configuration and does not revert Hoodi chain history; Glamsterdam did not activate on Hoodi. Hoodi operators were directed to follow revised execution- and consensus-client instructions rather than use the superseded activation schedule.[[20]](#cite-id-gmww6tirvn) Hoodi testing remains a future milestone with timing undecided; it is distinct from the Q4 2026 [mainnet](https://iq.wiki/wiki/mainnet) target, for which no activation date has been set. The Hoodi postponement does not itself determine a [mainnet](https://iq.wiki/wiki/mainnet) date.[[20]](#cite-id-gmww6tirvn)[[21]](#cite-id-k9edahsd40)\n\nDevelopers have indicated a willingness to adjust this timeline in response to bugs, finality issues, or client divergences uncovered on devnets and [testnets](https://iq.wiki/wiki/testnet), mirroring the cautious approach taken with the Pectra and Fusaka upgrades.[[12]](#cite-id-i53b1rvqsn)[[3]](#cite-id-rfAZoUE0K3) Formal security audits and community bug bounties focus on the period between public [testnet](https://iq.wiki/wiki/testnet) activation and final [mainnet](https://iq.wiki/wiki/mainnet) scheduling, with the [Ethereum](https://iq.wiki/wiki/ethereum) [Foundation](https://iq.wiki/wiki/foundation) announcement confirming bug bounty coverage around the Sepolia [fork](https://iq.wiki/wiki/fork).[[10]](#cite-id-r0wljdgupo)[[16]](#cite-id-dgvlv156ef) With Sepolia completed, developers describe the remaining Hoodi rehearsal and any follow-up testing as among the last major milestones before a [mainnet](https://iq.wiki/wiki/mainnet) activation decision; the Hoodi timing is undecided following its postponement.[[18]](#cite-id-sgo1al59yl)[[20]](#cite-id-gmww6tirvn)\n\n## Key Features\nGlamsterdam is expected to introduce several significant improvements to the [Ethereum](https://iq.wiki/wiki/ethereum) network, with much of its scope defined under Meta‑EIP‑7773 but still subject to final inclusion based on testing results. These features remain planned or under test and are not live on [mainnet](https://iq.wiki/wiki/mainnet).[[10]](#cite-id-r0wljdgupo) At a high level, the upgrade focuses on enshrined Proposer‑Builder Separation (ePBS), [block](https://iq.wiki/wiki/block)‑level access lists (BALs), and extensive [gas](https://iq.wiki/wiki/gas) repricing and accounting changes that better distinguish long‑term state growth from short‑term computation.[[16]](#cite-id-dgvlv156ef) Together, these changes are intended to increase Layer‑1 and blob throughput for rollups while keeping full [node](https://iq.wiki/wiki/node) requirements within reach of non‑specialized hardware.[[10]](#cite-id-r0wljdgupo)\n\nUnder Meta‑EIP‑7773, Glamsterdam’s Sepolia deployment tracks a set of EIPs scheduled for inclusion on that [testnet](https://iq.wiki/wiki/testnet), including ePBS (EIP‑7732), BALs (EIP‑7928), [gas](https://iq.wiki/wiki/gas) repricing for storage and hashing (such as EIP‑8037 and EIP‑8038), resource‑based intrinsic [gas](https://iq.wiki/wiki/gas) via EIP‑2780, [ETH](https://iq.wiki/wiki/ethereum) transfer logs (EIP‑7708), a deterministic factory predeploy (EIP‑7997), a SLOTNUM opcode and related execution changes, increased contract size limits, [validator](https://iq.wiki/wiki/validator) exit and churn tuning, exclusion of recently slashed proposers from [block](https://iq.wiki/wiki/block) production, and supporting networking EIPs required to propagate BALs and ePBS data.[[16]](#cite-id-dgvlv156ef)[[10]](#cite-id-r0wljdgupo) The announced scope may still evolve before [mainnet](https://iq.wiki/wiki/mainnet) activation, and some proposals, such as EIP‑7805 (FOCIL) or revisions to contract code size rules, are treated as “consider for inclusion” rather than guaranteed components of the Glamsterdam [fork](https://iq.wiki/wiki/fork).[[3]](#cite-id-rfAZoUE0K3)[[10]](#cite-id-r0wljdgupo) [EIP-8037](https://iq.wiki/wiki/eip-8037)’s and EIP-8038’s repricing is intended to reflect state resource costs and support capacity increases; review of their compatibility with existing contracts is a separate pre-mainnet concern that led developers to postpone Hoodi testing.[[20]](#cite-id-gmww6tirvn)[[22]](#cite-id-qi6jg8qae8)\n\nWithin this scope, **EIP‑7732 (ePBS)** remains the consensus‑layer headliner for Glamsterdam and is scheduled for inclusion in the upgrade but is not yet live on [mainnet](https://iq.wiki/wiki/mainnet).[[7]](#cite-id-ARj8e3zdv9)[[10]](#cite-id-r0wljdgupo) It formally separates [block](https://iq.wiki/wiki/block) proposers and builders and moves builder commitments and payments into the protocol, lengthening the data propagation and validation window and enabling larger payloads and higher throughput, especially for blob data used by Layer‑2 rollups.[[15]](#cite-id-v9ybl2h3bf)[[14]](#cite-id-kxie074qi8) ePBS introduces mechanisms such as a Payload Timeliness Committee (PTC) and dual‑deadline attestation logic to enforce timely [block](https://iq.wiki/wiki/block) delivery and strengthen liveness guarantees, while reducing reliance on external MEV relays and other centralized intermediaries in the [block](https://iq.wiki/wiki/block)‑building market.[[15]](#cite-id-v9ybl2h3bf)[[14]](#cite-id-kxie074qi8) A key challenge this EIP addresses is the \"free option problem,\" where builders can submit a [block](https://iq.wiki/wiki/block) commitment but choose not to reveal the full [block](https://iq.wiki/wiki/block) if market conditions become unfavorable, harming network liveness.\n\nGlamsterdam’s execution‑layer changes, including BALs, revised [gas](https://iq.wiki/wiki/gas) accounting, and resource‑based intrinsic [gas](https://iq.wiki/wiki/gas), are designed to encourage more efficient use of persistent state and to prepare [Ethereum](https://iq.wiki/wiki/ethereum) for higher parallelism and greater blob usage in subsequent roadmap phases.[[16]](#cite-id-dgvlv156ef)[[10]](#cite-id-r0wljdgupo) Cryptographic approaches to mitigating the ePBS free option problem, such as threshold encryption and silent threshold encryption, continue to be explored by researchers and projects like Shutter, but these mechanisms are not part of the core Glamsterdam [fork](https://iq.wiki/wiki/fork) and remain separate research directions that could influence later upgrades.[[9]](#cite-id-fqVa6HrtNK) Longer‑term ideas such as Verkle trees under “The [Verge](https://iq.wiki/wiki/verge)” roadmap and proposals to shorten [block](https://iq.wiki/wiki/block) times to 6 seconds are discussed in the broader [Ethereum](https://iq.wiki/wiki/ethereum) roadmap but are not scheduled components of the Glamsterdam [hard fork](https://iq.wiki/wiki/hard-fork) as defined in EIP‑7773.[[10]](#cite-id-r0wljdgupo)[[6]](#cite-id-M321njUVdJ)\n\n## Impact and Challenges\nGlamsterdam is framed by many core developers and commentators as the most significant protocol-level restructuring since The Merge, because it combines enshrined Proposer-Builder Separation with block-level parallel execution via BALs and extensive [gas](https://iq.wiki/wiki/gas) and state-cost repricing.[[14]](#cite-id-kxie074qi8)[[10]](#cite-id-r0wljdgupo) Devnet experiments and the Sepolia [testnet](https://iq.wiki/wiki/testnet) [fork](https://iq.wiki/wiki/fork), which raised Sepolia’s [gas](https://iq.wiki/wiki/gas) limit from around 60 million to about 200 million [gas](https://iq.wiki/wiki/gas) per [block](https://iq.wiki/wiki/block) with BAL-enabled execution, suggest that, if similar conditions hold on [mainnet](https://iq.wiki/wiki/mainnet), average transaction fees for many common operations could fall by roughly 70–80%, though these figures are projections from modeling and [testnet](https://iq.wiki/wiki/testnet) environments rather than guarantees for production networks.[[11]](#cite-id-a9o6skjpa2)[[17]](#cite-id-beh4cp90n1)[[18]](#cite-id-sgo1al59yl) The formal Sepolia schedule and its successful completion under bug bounty coverage signal that Glamsterdam has moved from design into full public testing. The Hoodi activation planned for October 26, 2026, was postponed on October 22 to investigate [EIP-8037](https://iq.wiki/wiki/eip-8037)’s interactions with [smart contracts](https://iq.wiki/wiki/smart-contract) deployed on [mainnet](https://iq.wiki/wiki/mainnet); no replacement date had been announced by November 3. Hoodi testing remains a future milestone with timing undecided, while the Q4 2026 [mainnet](https://iq.wiki/wiki/mainnet) target remains provisional and has no set activation date. Sepolia’s activation was not [mainnet](https://iq.wiki/wiki/mainnet) activation, and Hoodi’s postponement did not establish a mainnet date.[[16]](#cite-id-dgvlv156ef)[[20]](#cite-id-gmww6tirvn)[[21]](#cite-id-k9edahsd40)\n\nAt the same time, several risks and open questions remain as of November 2026. Researchers have highlighted potential builder-abuse vectors for ePBS on public [testnets](https://iq.wiki/wiki/testnet), including strategies that could exploit the longer timing window or attempt to game payload selection, and these behaviors were a focus of the completed Sepolia [fork](https://iq.wiki/wiki/fork); the timing of further Hoodi testing is undecided following its postponement.[[13]](#cite-id-ypk7yvpviw)[[20]](#cite-id-gmww6tirvn) Developers also postponed the Hoodi activation to investigate how EIP-8037’s state-creation [gas](https://iq.wiki/wiki/gas) accounting interacts with [smart contracts](https://iq.wiki/wiki/smart-contract) deployed on mainnet.[[20]](#cite-id-gmww6tirvn) Client teams also face tight timelines between releasing stable Glamsterdam-ready versions and activating them on each [testnet](https://iq.wiki/wiki/testnet), increasing the importance of coordinated testing and rollback plans.[[12]](#cite-id-i53b1rvqsn) More broadly, the absence of a fixed [mainnet](https://iq.wiki/wiki/mainnet) date despite the Q4 2026 target underlines developers’ willingness to delay activation if devnet or [testnet](https://iq.wiki/wiki/testnet) results reveal unresolved issues.[[21]](#cite-id-k9edahsd40)\n\nFor investors, successful upgrades can enhance network efficiency and utility, potentially strengthening the long-term value proposition of [Ethereum](https://iq.wiki/wiki/ethereum) (ETH), while setbacks or delays may briefly increase uncertainty but can also signal a preference for safety over speed. For developers, Glamsterdam’s new [EIPs](https://iq.wiki/wiki/ethereum-improvement-proposal-eip)—including ePBS, BALs, and revised [gas](https://iq.wiki/wiki/gas) accounting—introduce new functionalities, tools, and optimizations that may require substantial code changes but open the door to more sophisticated, efficient, and secure [decentralized applications](https://iq.wiki/wiki/decentralized-application). For users, the upgrade’s net effect is expected to be a more stable, secure, and potentially faster and cheaper network experience over time, with any short-term complexity during the transition balanced against long-term capacity gains.\n\nDespite the anticipated benefits, coordinating a [hard fork](https://iq.wiki/wiki/hard-fork) for a network as large and complex as [Ethereum](https://iq.wiki/wiki/ethereum) presents significant challenges. Thousands of contributors must ensure backward compatibility, maintain client diversity, and rigorously test every change. The decision to defer EIP-7907 from [Fusaka](https://iq.wiki/wiki/fusaka) and to treat elements of Glamsterdam’s scope as conditional on [testnet](https://iq.wiki/wiki/testnet) results underscores this complexity and demonstrates developers' commitment to caution and thoroughness over rushed implementation. Another key challenge is ensuring that as [Ethereum](https://iq.wiki/wiki/ethereum) scales, it preserves its core ethos, including censorship resistance and privacy, which some developers have raised concerns about if not explicitly reaffirmed as strategic goals.\n\n[Tim Beiko](https://iq.wiki/wiki/tim-beiko), a project coordinator, stated, \"Protocol is now a more united and leaner organization with more focused teams…ensuring the EF’s resources are allocated toward maximal impact.\" He also noted, \"[Ethereum](https://iq.wiki/wiki/ethereum) stands at the edge of major breakthroughs…This may be our best shot at deploying not only our technology, but our values, at planetary scale.\" [Ansgar Dietrichs](https://iq.wiki/wiki/ansgar-dietrichs) added, \"For Glamsterdam…we will have to find some ways to continue the blob scaling…there might be some EL-side scaling opportunities too.\" These statements highlight the strategic importance and ambitious goals of the Glamsterdam upgrade.[[2]](#cite-id-LOWNMso5Cb)[[3]](#cite-id-rfAZoUE0K3)\n\n### Gas-Repricing Compatibility Review\n[EIP-8037](https://iq.wiki/wiki/eip-8037) introduces separate accounting for state creation, including a state-gas reservoir, while EIP-8038 reprices state access. Under the proposed EIP-8037 accounting, reservoir funding is distinct from execution [gas](https://iq.wiki/wiki/gas) reported by `gasleft()`. Clearing storage created earlier in a transaction can refill execution gas, up to outstanding execution-funded state-creation charges; a reverting intermediary can also restore execution-funded state-creation charges. These changes can alter the execution gas available after a failed external call and affect contracts that check remaining gas after calls or depend on a failure handler running out of gas.[[23]](#cite-id-1igzuqbiyw)\n\nFor example, an insufficient-gas external call that previously left too little gas for a failure handler and forced a retry or revert may, under the proposed accounting, leave enough execution gas for the handler to complete and commit a failure. These are conditional behaviors, not a claim that all contracts using external calls or gas checks are vulnerable. Correctly bounded pre-call gas checks can still work if their budget covers the permitted paths and the forwarding overhead is revalidated under the new schedule. ChainSecurity recommends reviewing failure-handling paths and testing them against the changed rules.[[23]](#cite-id-1igzuqbiyw)\n\nChainSecurity said it had identified 13 real-world examples and was conducting responsible disclosure; the examples were reported as potentially affected cases, not as 13 confirmed exploits.[[24]](#cite-id-1q8zqkwnx4) The [Ethereum](https://iq.wiki/wiki/ethereum) [Foundation](https://iq.wiki/wiki/foundation)’s historical [mainnet](https://iq.wiki/wiki/mainnet) replay analysis found that the large majority of contracts were unaffected. Many flagged cases could be addressed by raising gas limits, while a smaller set relying on fixed gas stipends, hardcoded gas values, `gasleft()` branches, or gas-sensitive failure handling might require code changes. Application teams were advised to inspect affected-contract results, review flagged call sites, test changes on the Glamsterdam devnet, and update gas estimation.[[22]](#cite-id-qi6jg8qae8)","recentActivity":null,"operator":{"id":"0x1e23b34d3106f0c1c74d17f2cd0f65cdb039b138"},"categories":[{"id":"glossary","title":"glossary"}],"tags":[],"images":[{"id":"QmRSmLhJ63amSNFFoAxk4SDYUUF1Y8EXMsGFQoYntb6Baf","type":"image/jpeg, image/png"}],"media":[{"name":null,"id":"QmQZi4ok8uhRS1UN9XXr6bvmfqRxAGndQQdapMDuDAc9TL","size":null,"type":"GALLERY","source":"IPFS_IMG"},{"name":null,"id":"QmTy7tRS6c9BNMz4CSUpVGPaXBNgN4hMypQsL6877BZrSd","size":null,"type":"GALLERY","source":"IPFS_IMG"},{"name":null,"id":"QmbyqM5f2Vni4dQcC26optETjBWnTfcwwjPxAKPGExBRor","size":null,"type":"GALLERY","source":"IPFS_IMG"},{"name":"a-clean-and-modern-digital-illustration-_CC2N8MlrQ56vCyDuaKinnA_b1ji6tOkRV6bUC4DmRnpHg.jpeg","id":"QmYiK7JpHoCmPudF6Je89SStggZHugT869VUaeGukvExFn","size":null,"type":null,"source":"IPFS_IMG"},{"name":"a-digital-illustration-of-the-ethereum-l_dS8vmt-zSS-BDsX_8jeUMw_b1ji6tOkRV6bUC4DmRnpHg.jpeg","id":"QmNvY3Gvivr71qLCcdoGtTYwWmCJrKGqoHb7VxeQrK3ZYT","size":null,"type":null,"source":"IPFS_IMG"},{"name":"Hfz4xubm6kc","id":"https://www.youtube.com/watch?v=Hfz4xubm6kc","size":null,"type":null,"source":"YOUTUBE"}],"linkedWikis":{"founders":[],"blockchains":["ethereum"],"speakers":[]},"events":[{"id":"f1c287c2-feb7-4b4d-8dc6-c3bac2ecb0d3","type":"DEFAULT","date":"2025-01-01","multiDateStart":null,"multiDateEnd":null,"country":"","continent":"","title":"Glamsterdam Name Proposed","description":"The name “Glamsterdam” was proposed, combining the star Gloas with the Devconnect city Amsterdam for the post‑Fusaka upgrade.","link":"https://etherworld.co/2025/01/09/glamsterdam-the-next-upgrade-after-fusaka/"},{"id":"afff139c-936f-47cc-9ae4-78cfdc4cad11","type":"DEFAULT","date":"2025-08-01","multiDateStart":null,"multiDateEnd":null,"country":null,"continent":null,"title":"Glamsterdam Headliner Selected: EIP-7732 (ePBS)","description":"All Core Developers Consensus Call #162 selected EIP-7732 enshrined proposer-builder separation (ePBS) as Glamsterdam’s consensus-layer headliner.","link":"https://etherworld.co/2025/08/11/eip-7732-epbs-selected-as-glamsterdam-headliner/"},{"id":"d713a42b-5d6a-4097-9b80-e441460dd7c7","type":"DEFAULT","date":"2025-08-01","multiDateStart":null,"multiDateEnd":null,"country":null,"continent":null,"title":"Glamsterdam Specification Freeze Deadline","description":"Regular EIP proposal and specification deadline was August 21, 2025, ahead of devnet and testnet phases.","link":"https://etherworld.co/2025/07/18/ethereum-sets-sights-on-glamsterdam-post-fusaka-rollout/"},{"id":"34512226-d20a-4e81-96c1-429694eacaf2","type":"DEFAULT","date":"2026-06-01","multiDateStart":null,"multiDateEnd":null,"country":"","continent":"","title":"Glamsterdam Devnets Enter Final Phase","description":"Ethereum core developers began running devnets with the full Glamsterdam EIP set, describing it as the largest fork since the Merge.","link":"https://www.coindesk.com/tech/2026/06/16/ethereum-s-biggest-protocol-overhaul-in-years-moves-into-its-final-development-stage"},{"id":"f8b4d2dd-ec41-4f7e-8ddc-6927d4b36e0b","type":"DEFAULT","date":"2026-09-01","multiDateStart":null,"multiDateEnd":null,"country":null,"continent":null,"title":"Glamsterdam Sepolia Testnet Announced","description":"The Ethereum Foundation published the Sepolia activation schedule: epoch 353,024, slot 11,296,768, corresponding to October 6, 2026, 13:53:36 UTC.","link":"https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement"},{"id":"e5b77194-6fa0-4f11-b493-d1bd9edc3670","type":"DEFAULT","date":"2026-10-01","multiDateStart":null,"multiDateEnd":null,"country":null,"continent":null,"title":"Glamsterdam Sepolia Testnet Activation","description":"Glamsterdam activated on Sepolia on October 6, 2026, at epoch 353,024 and slot 11,296,768; the test raised the gas limit to 200 million.","link":"https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement"},{"title":"Glamsterdam Hoodi Testnet Activation Postponed","date":"2026-10-01","type":"DEFAULT","description":"On October 22, 2026, developers postponed the Hoodi activation scheduled for October 26 to investigate EIP-8037’s interactions with deployed mainnet contracts. No replacement Hoodi date was announced.","link":"https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay","country":null,"continent":null,"multiDateStart":null,"multiDateEnd":null,"id":"08e3711d-b147-4052-8496-0527fe9a4fb2"}],"founderWikis":[],"blockchainWikis":[{"id":"ethereum","title":"Ethereum"}],"metadata":[{"id":"website","value":"https://ethereum.foundation/"},{"id":"words-changed","value":"534"},{"id":"percent-changed","value":"27.38"},{"id":"blocks-changed","value":"content, tags, summary"},{"id":"wiki-score","value":"88"},{"id":"references","value":"[{\"id\":\"3imVvYHRKv\",\"url\":\"https://etherworld.co/2025/01/09/glamsterdam-the-next-upgrade-after-fusaka/\",\"description\":\"Glamsterdam: The Next Upgrade After Fusaka\",\"timestamp\":1753820060785},{\"id\":\"LOWNMso5Cb\",\"url\":\"https://blockworks.co/news/ethereum-glamsterdam-hard-fork\",\"description\":\"Ethereum refactors itself for Glamsterdam hard fork\",\"timestamp\":1753820060785},{\"id\":\"rfAZoUE0K3\",\"url\":\"https://www.ainvest.com/news/ethereum-news-today-ethereum-defers-eip-7907-glamsterdam-hard-fork-2507/\",\"description\":\"Ethereum defers EIP-7907 for Glamsterdam Hard Fork\",\"timestamp\":1753820060785},{\"id\":\"1otWM0BVGC\",\"url\":\"https://etherworld.co/2025/07/18/ethereum-sets-sights-on-glamsterdam-post-fusaka-rollout/\",\"description\":\"Ethereum Sets Sights on Glamsterdam Post-Fusaka Rollout\",\"timestamp\":1753820060785},{\"id\":\"lbk79tETJu\",\"url\":\"https://cointelegraph.com/news/ethereum-s-fusaka-fork-tipped-for-november-as-glamsterdam-comes-into-view\",\"description\":\"Ethereum’s Fusaka upgrade set for November, Glamsterdam planning next\",\"timestamp\":1753820060785},{\"id\":\"M321njUVdJ\",\"url\":\"https://cointelegraph.com/explained/vitalik-buterins-vision-for-ethereum-pectra-glamsterdam-and-beyond\",\"description\":\"Vitalik Buterin’s vision for Ethereum: Pectra, Glamsterdam and beyond\",\"timestamp\":1753820060785},{\"id\":\"ARj8e3zdv9\",\"url\":\"https://etherworld.co/2025/08/11/eip-7732-epbs-selected-as-glamsterdam-headliner/\",\"description\":\"EIP-7732 (ePBS) Selected as Glamsterdam Headliner\",\"timestamp\":1758040332619},{\"id\":\"jRI3wv4V9g\",\"url\":\"https://cryptoslate.com/ethereums-q4-fusaka-upgrade-at-risk-as-developers-fixate-on-2026-glamsterdam-plans/\",\"description\":\"Concerns over Glamsterdam focus affecting Fusaka\",\"timestamp\":1758040504472},{\"id\":\"fqVa6HrtNK\",\"url\":\"https://blog.shutter.network/shutters-perspective-on-glamsterdam-and-a-cryptographic-fix-for-epbss-free-option-problem/\",\"description\":\"Cryptographic fix for ePBS's free option problem\",\"timestamp\":1758040504472},{\"id\":\"r0wljdgupo\",\"url\":\"https://ethereum.org/roadmap/glamsterdam/\",\"description\":\"Ethereum.org Glamsterdam roadmap\",\"timestamp\":1790648275362},{\"id\":\"a9o6skjpa2\",\"url\":\"https://cryptobriefing.com/ethereum-glamsterdam-upgrade-october-test/\",\"description\":\"Ethereum Sets Oct. 6 Sepolia test for Glamsterdam\",\"timestamp\":1790648275362},{\"id\":\"i53b1rvqsn\",\"url\":\"https://optimisus.com/news/blockchain-news/ethereums-glamsterdam-upgrade-now-has-a-sepolia-date-the-biggest-changes-are-moving-from-design-to-testing/\",\"description\":\"Ethereum’s Glamsterdam upgrade now has a Sepolia date\",\"timestamp\":1790648275362},{\"id\":\"ypk7yvpviw\",\"url\":\"https://adbytes.media/blog/ethereum-sets-oct-6-sepolia-fork-for-glamsterdam-as-epbs-abuse-fears-grow\",\"description\":\"Ethereum sets Oct. 6 Sepolia fork as ePBS abuse fears grow\",\"timestamp\":1790648275362},{\"id\":\"kxie074qi8\",\"url\":\"https://cryptoexpo.net/articles/ethereum-glamsterdam-upgrade-a-deep/\",\"description\":\"Ethereum Glamsterdam upgrade deep dive\",\"timestamp\":1790648275362},{\"id\":\"v9ybl2h3bf\",\"url\":\"https://blazed.sh/blog/posts/epbs-eip-7732-searchers-builders/\",\"description\":\"ePBS (EIP-7732) for searchers and builders\",\"timestamp\":1790648275362},{\"id\":\"dgvlv156ef\",\"url\":\"https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement\",\"description\":\"Ethereum Foundation Glamsterdam Sepolia testnet announcement\",\"timestamp\":1790648430888},{\"id\":\"beh4cp90n1\",\"url\":\"https://www.coindesk.com/tech/2026/10/06/ethereum-s-glamsterdam-test-gets-last-minute-fix-before-major-capacity-jump\",\"description\":\"Ethereum’s Glamsterdam test gets last-minute fix before major capacity jump\",\"timestamp\":1791389354112},{\"id\":\"sgo1al59yl\",\"url\":\"https://cointelegraph.com/news/ethereums-glamsterdam-upgrade-launches-on-sepolia-testnet\",\"description\":\"Ethereum’s Glamsterdam upgrade launches on Sepolia testnet\",\"timestamp\":1791389491824},{\"id\":\"ox1v5bhc61\",\"url\":\"https://ethdaily.io/glamsterdam-activates-on-sepolia-testnet\",\"description\":\"Glamsterdam activates on Sepolia testnet – EthDaily\",\"timestamp\":1791389491824},{\"id\":\"gmww6tirvn\",\"url\":\"https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay\",\"description\":\"Ethereum Foundation Glamsterdam Hoodi delay\",\"timestamp\":1792852298270},{\"id\":\"k9edahsd40\",\"url\":\"https://ethereum.org/roadmap/\",\"description\":\"Ethereum.org roadmap\",\"timestamp\":1793708302471},{\"id\":\"qi6jg8qae8\",\"url\":\"https://blog.ethereum.org/2026/08/24/glamsterdam-repricing-testing\",\"description\":\"Ethereum Foundation Glamsterdam repricing testing guidance\",\"timestamp\":1793708302472},{\"id\":\"1igzuqbiyw\",\"url\":\"https://www.chainsecurity.com/blog/glamsterdam-gas/\",\"description\":\"ChainSecurity Glamsterdam gas analysis\",\"timestamp\":1793708302472},{\"id\":\"1q8zqkwnx4\",\"url\":\"https://defiprime.com/glamsterdam-hoodi-delay-gas-failure-handlers\",\"description\":\"DefiPrime report on gas-handling risks\",\"timestamp\":1793708302472}]"},{"id":"previous_cid","value":"QmWQ2g8aarAxsMdV5QcyH6ChghpbhLanqS9DzmbHhQGstt"},{"id":"commit-message","value":"Expand the Ethereum Glamsterdam Upgrade timeline"},{"id":"previous_cid","value":"QmWQ2g8aarAxsMdV5QcyH6ChghpbhLanqS9DzmbHhQGstt"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x1e23b34d3106f0c1c74d17f2cd0f65cdb039b138"},"views":2099}