{"id":"ethereum-glamsterdam-upgrade","hidden":false,"ipfs":"QmVzfZU5CExwnbLyQqXZPGbDohFw2J6tVwjhkhNMd9WTs5","language":"en","transactionHash":"0x25cb83c335ace809610674b29a57b028e986bc3f00a2c138608e2a0c64c1adc6","created":"2025-07-29T20:33:15.867Z","updated":"2025-09-16T16:37:48.769Z","title":"Ethereum Glamsterdam Upgrade","summary":"Glamsterdam is an upcoming Ethereum hard fork after Fusaka that adds enshrined proposer–builder separation (ePBS), block‑level access lists, and gas and state‑cost repricing to boost throughput and lower fees, with Sepolia testing in October 2026.","content":"**Glamsterdam** is an upcoming major [hard fork](https://iq.wiki/wiki/hard-fork) of the [Ethereum](https://iq.wiki/wiki/ethereum) [blockchain](https://iq.wiki/wiki/blockchain), designed to enhance its scalability, security, and sustainability. It is the Execution Layer (EL) network upgrade that follows the Fusaka upgrade and is targeted for [mainnet](https://iq.wiki/wiki/mainnet) activation in Q4 2026, although no specific [mainnet](https://iq.wiki/wiki/mainnet) date or epoch has been set. As of September 2026, Glamsterdam has progressed through multiple private developer [test networks](https://iq.wiki/wiki/testnet) and is preparing for a public Sepolia [testnet](https://iq.wiki/wiki/testnet) [fork](https://iq.wiki/wiki/fork). The name \"Glamsterdam\" is derived from combining the star Gloas with Amsterdam, the city where a recent Devconnect event took place.[[1]](#cite-id-3imVvYHRKv)[[11]](#cite-id-r0wljdgupo)[[12]](#cite-id-a9o6skjpa2)\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 targeted for a Q4 2026 [mainnet](https://iq.wiki/wiki/mainnet) activation, with exact timing to be finalized after public [testnet](https://iq.wiki/wiki/testnet) validation.[[11]](#cite-id-r0wljdgupo)[[5]](#cite-id-lbk79tETJu) 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.[[17]](#cite-id-dgvlv156ef)[[11]](#cite-id-r0wljdgupo) In advance of this [fork](https://iq.wiki/wiki/fork), [node](https://iq.wiki/wiki/node) operators are required to update both their execution and consensus clients to Sepolia‑compatible releases.[[17]](#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 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\n\nThe Glamsterdam upgrade is positioned as the successor to the [Fusaka](https://iq.wiki/wiki/fusaka) upgrade, which is tentatively scheduled for [mainnet](https://iq.wiki/wiki/mainnet) deployment in early November 2025. [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.[[4]](#cite-id-1otWM0BVGC)[[5]](#cite-id-lbk79tETJu)\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.[[12]](#cite-id-a9o6skjpa2)[[13]](#cite-id-i53b1rvqsn)\n\nOn September 17, 2026, the [Ethereum Foundation](https://iq.wiki/wiki/ethereum-foundation-ef) announced that the Glamsterdam upgrade is 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.[[17]](#cite-id-dgvlv156ef) The same announcement stated that activation times for the Hoodi [testnet](https://iq.wiki/wiki/testnet) and the [Ethereum](https://iq.wiki/wiki/ethereum) [mainnet](https://iq.wiki/wiki/mainnet) remain to be determined and will be communicated separately, so the Sepolia scheduling updates earlier, more generic plans but does not itself set a [mainnet](https://iq.wiki/wiki/mainnet) epoch or date.[[17]](#cite-id-dgvlv156ef) 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 targeting a Q4 2026 [mainnet](https://iq.wiki/wiki/mainnet) activation, but as of September 2026 no specific [mainnet](https://iq.wiki/wiki/mainnet) date or epoch has been confirmed.[[11]](#cite-id-r0wljdgupo)\n\nDevelopers have indicated a willingness to adjust this timeline in response to bugs, finality issues, or client divergences uncovered on devnets and testnets, mirroring the cautious approach taken with the Pectra and Fusaka upgrades.[[13]](#cite-id-i53b1rvqsn)[[3]](#cite-id-rfAZoUE0K3) Formal security audits and community bug bounties are expected to focus on the period between public testnet activation and final mainnet scheduling, with the Ethereum [Foundation](https://iq.wiki/wiki/foundation) announcement confirming bug bounty coverage around the Sepolia [fork](https://iq.wiki/wiki/fork).[[11]](#cite-id-r0wljdgupo)[[17]](#cite-id-dgvlv156ef)\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 by mid‑2026 but still subject to final inclusion based on testing results. A primary focus of the upgrade is the transition from [Merkle trees](https://iq.wiki/wiki/merkle-tree) to Verkle trees, which is intended to enhance how [Ethereum](https://iq.wiki/wiki/ethereum) stores data and validates transactions, paving the way for greater scalability and efficiency. Verkle trees are a critical component of [Ethereum](https://iq.wiki/wiki/ethereum)'s \"The [Verge](https://iq.wiki/wiki/verge)\" phase, which aims to make state access more efficient and enable stateless [block](https://iq.wiki/wiki/block) verification.[[11]](#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 enshrined proposer–builder separation (EIP‑7732), block-level access lists (EIP‑7928), pricing and state‑growth changes (EIP‑8037 and EIP‑8038), [validator](https://iq.wiki/wiki/validator) churn improvements (for example, EIP‑8061), and related execution- and consensus-layer proposals.[[17]](#cite-id-dgvlv156ef) The announcement also notes that this scope may still change before [mainnet](https://iq.wiki/wiki/mainnet) activation and that activation parameters for the Hoodi [testnet](https://iq.wiki/wiki/testnet) and [mainnet](https://iq.wiki/wiki/mainnet) are not yet finalized.[[17]](#cite-id-dgvlv156ef)\n\nOther EIPs and features that are scheduled for inclusion or considered within the Glamsterdam scope include:\n\n* **EIP-7702 (Set EOA account code for one transaction)** – Expected to give externally owned accounts a temporary code slot for a single transaction, enabling more flexible wallet designs while preserving the existing account model.[[10]](#cite-id-BP8XkUEcvV)\n* **EIP-7928 (Block-Level Access Lists, BALs)** – A major execution-layer feature that lets [block](https://iq.wiki/wiki/block) proposers publish block-level state access declarations, allowing clients to prefetch and schedule work more safely for parallel execution within a [block](https://iq.wiki/wiki/block).[[13]](#cite-id-i53b1rvqsn)[[15]](#cite-id-kxie074qi8)\n* **State-cost and [gas](https://iq.wiki/wiki/gas) repricing (for example, EIP‑8037 and EIP‑8038)** – A set of proposals under the Glamsterdam umbrella that aim to limit long‑term state growth and rebalance [gas](https://iq.wiki/wiki/gas) costs for storage and hashing, with exact parameter choices and the final EIP set still subject to confirmation after [testnet](https://iq.wiki/wiki/testnet) evaluation.[[13]](#cite-id-i53b1rvqsn)[[11]](#cite-id-r0wljdgupo)\n* **Networking and execution support for BALs (such as EIP‑8159)** – Expected changes to execution-layer gossip and validation rules so that block-level access lists can be propagated, verified, and used by clients without introducing unsafe assumptions or excessive complexity.[[13]](#cite-id-i53b1rvqsn)\n* **[Validator](https://iq.wiki/wiki/validator) churn and exit scaling (for example, EIP‑8061)** – Proposed adjustments so that validator entry, exit, and consolidation capacity scales more directly with total ETH staked, improving responsiveness of the validator set without compromising safety thresholds.[[13]](#cite-id-i53b1rvqsn)\n* **EIP-7932 (Add BLOBBASEFEE opcode)**\n* **EIP-7938 (BLOBHASH precompile)**\n* **EIP-7940 (SSZ Withdrawal Root)**\n* **EIP-7941 (SSZ Receipts Root)**\n* **EIP-7942 (SSZ Transactions Root)**\n* **EIP-7732 (ePBS - enshrined Proposer-Builder Separation):** Selected as the consensus-layer headliner for Glamsterdam, this EIP is scheduled for inclusion in the upgrade but is not yet live on [mainnet](https://iq.wiki/wiki/mainnet).[[7]](#cite-id-ARj8e3zdv9)[[11]](#cite-id-r0wljdgupo) It formally separates block proposers and builders and moves builder commitments and payments into the protocol, expanding the data propagation and validation window from roughly 2 seconds to around 9 seconds and enabling larger payloads and higher throughput, especially for blob data used by Layer‑2 rollups.[[16]](#cite-id-v9ybl2h3bf)[[15]](#cite-id-kxie074qi8) ePBS introduces mechanisms such as a Payload Timeliness Committee (PTC) and dual-deadline attestation logic to enforce timely block delivery and strengthen liveness guarantees, while reducing reliance on external MEV relays and other centralized intermediaries in the block-building market.[[16]](#cite-id-v9ybl2h3bf)[[15]](#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* **EIP-7805 (FOCIL - Fork-Choice Enforced Inclusion Lists):** Marked as 'Consider for Inclusion' (CFI) for the Glamsterdam upgrade, FOCIL is designed to introduce stronger user experience (UX) guarantees and enhance censorship resistance within the network.[[7]](#cite-id-ARj8e3zdv9)\n* **Gas optimizations and protocol-level efficiency:** Glamsterdam is expected to focus on making [Ethereum](https://iq.wiki/wiki/ethereum) faster and cheaper to use, particularly for complex applications like Layer‑2 rollups and zero-knowledge (ZK) technology, through a combination of execution parallelism, blobspace expansion, and revised gas accounting.[[11]](#cite-id-r0wljdgupo)[[15]](#cite-id-kxie074qi8)\n* **EIP-7907 (Contract Code Size Limits):** Although deferred from the Fusaka upgrade to prioritize stability, a revised version of EIP-7907, which addresses contract code size limits and introduces [gas](https://iq.wiki/wiki/gas) metering changes, remains under consideration for future implementation in Glamsterdam or subsequent upgrades, highlighting developers' preference for extensive testing before deployment.[[3]](#cite-id-rfAZoUE0K3)\n* **Reduced Block Time:** [Ethereum](https://iq.wiki/wiki/ethereum) core developer Barnabé Monnot has proposed reducing the [block](https://iq.wiki/wiki/block) time from the current 12 seconds to 6 seconds. If eventually approved for a future [hard fork](https://iq.wiki/wiki/hard-fork), this change could significantly improve user experience and enhance the efficiency of [decentralized finance (DeFi)](https://iq.wiki/wiki/defi) applications, but by 2026 it was being discussed as a possible long‑term direction rather than a feature firmly scheduled for Glamsterdam.[[1]](#cite-id-3imVvYHRKv)[[2]](#cite-id-LOWNMso5Cb)[[6]](#cite-id-M321njUVdJ)\n\nCryptographic 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)\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.[[15]](#cite-id-kxie074qi8)[[11]](#cite-id-r0wljdgupo) Devnet experiments targeting a ~200 million [gas](https://iq.wiki/wiki/gas) limit with BAL-enabled parallel 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 test environments rather than guarantees for production networks.[[12]](#cite-id-a9o6skjpa2)[[15]](#cite-id-kxie074qi8) The formal Sepolia schedule and associated bug bounty coverage signal that Glamsterdam has moved from design into full public testing, but successful Sepolia and later Hoodi rehearsals remain prerequisites before any [mainnet](https://iq.wiki/wiki/mainnet) date is confirmed.[[17]](#cite-id-dgvlv156ef)\n\nAt the same time, several risks and open questions remain as of September 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 are a focus of the upcoming Sepolia and Hoodi [forks](https://iq.wiki/wiki/fork).[[14]](#cite-id-ypk7yvpviw) Client teams also face tight timelines between releasing stable Glamsterdam-ready versions and activating them on Sepolia, increasing the importance of coordinated testing and rollback plans.[[13]](#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.[[11]](#cite-id-r0wljdgupo)\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 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 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)","recentActivity":null,"operator":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"categories":[{"id":"cryptoassets","title":"cryptoassets"}],"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 Execution Layer upgrade.","link":"https://etherworld.co/2025/01/09/glamsterdam-the-next-upgrade-after-fusaka/"},{"title":"Glamsterdam Headliner Selected: EIP-7732 (ePBS)","date":"2025-08-01","type":"DEFAULT","description":"Ethereum core developers chose EIP-7732 enshrined proposer–builder separation as Glamsterdam’s consensus-layer headliner during All Core Developers Consensus call #162.","link":"https://etherworld.co/2025/08/11/eip-7732-epbs-selected-as-glamsterdam-headliner/","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"afff139c-936f-47cc-9ae4-78cfdc4cad11"},{"title":"Glamsterdam Specification Freeze Deadline","date":"2025-08-01","type":"DEFAULT","description":"Deadline set to finalize Glamsterdam headliners and regular EIPs, limiting scope before devnet and testnet phases.","link":"https://etherworld.co/2025/07/18/ethereum-sets-sights-on-glamsterdam-post-fusaka-rollout/","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"d713a42b-5d6a-4097-9b80-e441460dd7c7"},{"title":"Glamsterdam Sepolia Testnet Announced","date":"2026-09-01","type":"DEFAULT","description":"Ethereum Foundation announced Glamsterdam’s Sepolia activation at epoch 353,024, slot 11,296,768, scheduled for October 6, 2026.","link":"https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"f8b4d2dd-ec41-4f7e-8ddc-6927d4b36e0b"},{"title":"Glamsterdam Sepolia Testnet Activation","date":"2026-10-01","type":"DEFAULT","description":"Glamsterdam upgrade scheduled to activate on Sepolia at epoch 353,024, slot 11,296,768 (13:53:36 UTC) as a full public test before mainnet.","link":"https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"e5b77194-6fa0-4f11-b493-d1bd9edc3670"}],"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\":\"BP8XkUEcvV\",\"url\":\"https://etherworld.co/2025/08/25/expected-eips-in-glamsterdam-upgrade-execution-layer/\",\"description\":\"Expected EIPs in Glamsterdam Upgrade\",\"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":"previous_cid","value":"QmVzfZU5CExwnbLyQqXZPGbDohFw2J6tVwjhkhNMd9WTs5"},{"id":"commit-message","value":"Update Glamsterdam Upgrade: expand summary, timeline, and tags"},{"id":"previous_cid","value":"QmVzfZU5CExwnbLyQqXZPGbDohFw2J6tVwjhkhNMd9WTs5"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"views":1622}