Ethereum’s ambitious scaling and protocol optimization roadmap is moving forward as core developers formally schedule the Glamsterdam network upgrade for the Hoodi testnet. Following a successful deployment on the Sepolia testnet on October 6, 2026, the upcoming upgrade will hit Hoodi at epoch 132,352, corresponding to slot 4,235,264, which is currently slated for October 26, 2026, at 17:42:48 UTC. Alongside this activation, the Hoodi network’s gas limit will be increased to 200 million, mirroring the parameters established during the Sepolia deployment. While testnet momentum is building, a definitive mainnet activation date remains undetermined and will be announced by client teams once testing metrics are fully evaluated.
Node operators running infrastructure on Hoodi are facing a mandatory software upgrade window. Both execution layer and consensus layer clients must be updated to compatible versions before the scheduled epoch and slot parameters are reached. Client teams are actively rolling out updated software releases that incorporate the necessary protocol modifications. Network administrators and stakers have been strongly advised to verify that their chosen software builds explicitly support the Hoodi Glamsterdam activation to avoid network desynchronization or unintended validation penalties.
Glamsterdam Overview and Core Protocol Changes
The Glamsterdam upgrade represents a major milestone for Ethereum by merging the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. Together, these modifications introduce structural shifts designed to enhance layer-one throughput, optimize validator operations, and refine resource accounting across the entire network. The headlining features of the upgrade include enshrined proposer-builder separation and block-level access lists, both of which fundamentally alter how blocks are proposed, validated, and processed on the blockchain.
Enshrined Proposer-Builder Separation
One of the most significant structural changes introduced in Glamsterdam is enshrined proposer-builder separation, operationalized through EIP-7732. Historically, the division of labor between block proposers and external block builders has relied on trusted auxiliary middleware and off-protocol relays. By bringing this architecture directly into Ethereum’s core consensus protocol, the network standardizes the interaction. Under the new rules, a block proposer includes a builder’s cryptographic commitment to an execution payload, and the builder subsequently reveals the payload within a defined timeframe.
Crucially, the protocol itself manages the payment settlement to the proposer, minimizing counterparty risk and reducing reliance on external trusted parties. Furthermore, EIP-7732 decouples consensus validation from execution validation. This separation grants validator nodes significantly more time to verify execution payloads without risking consensus delays. A newly established payload timeliness committee is tasked with attesting to whether builders successfully revealed their payloads and whether corresponding blob data was available on time. Validator operators and engineering teams maintaining builder infrastructure are urged to review these revised operational duties and network interfaces thoroughly.
Block-Level Access Lists
Complementing proposer-builder separation, EIP-7732 introduces block-level access lists to streamline data retrieval and transaction verification. These enforced lists systematically record all accounts and storage locations accessed over the course of a block, alongside their respective post-transaction state changes. By providing explicit visibility into state dependencies ahead of time, execution clients gain the ability to read state data from disk in parallel, validate incoming transactions concurrently, and compute state roots with greater computational efficiency. Together, enshrined proposer-builder separation and block-level access lists establish a robust foundation for scaling Ethereum’s native execution capacity while ensuring that running an independent node remains practical for operators.
Gas Pricing and State Growth Adjustments
Glamsterdam also introduces comprehensive updates to Ethereum’s gas accounting mechanisms to align transaction costs more closely with underlying resource consumption and state bloat. Through EIP-8037, the network increases and separately meters the financial and computational costs associated with creating new state, directly addressing long-term state growth concerns. Simultaneously, EIP-8038 updates general state-access costs. Additional modifications cover intrinsic transaction fees, calldata processing, access lists, and broader block gas accounting rules.
Because of these structural adjustments, application developers and smart contract engineers must thoroughly test their code and gas estimations against the updated rules. Contracts that rely on fixed gas stipends, hardcoded gas limits, or rigid assumptions regarding remaining execution gas may experience unexpected failures and will likely require code modifications. Developers can consult the official Glamsterdam repricing impact guide to search for affected contracts and access testing documentation.
Developer and Validator Improvements
Beyond the headline changes, Glamsterdam packs a variety of developer-facing and validator-centric enhancements. The upgrade incorporates native Ethereum transfer logs, a dedicated slot-number opcode, an increased maximum contract size limit, a deterministic factory contract, and newly introduced stack-manipulation instructions. On the consensus side, protocol updates feature forward-compatible data structures, provisions to exclude slashed validators from proposing new blocks, and an increased rate of exit and consolidation churn to maintain validator set dynamism.
Specifications and Security Framework
The technical parameters of the upgrade are tracked under EIP-7773, which outlines the comprehensive list of included execution and consensus layer improvements, alongside supporting networking and informational specifications.
To ensure the robustness of the upgrade, the Ethereum Bug Bounty Program has been extended to cover all Glamsterdam specifications and associated EIPs. Client software implementations become eligible for bug bounty rewards as soon as their respective releases are officially published and linked in the network’s deployment tables. Security researchers and developers are encouraged to review the main Ethereum bug bounty portal for detailed information regarding reward multipliers, vulnerability submission requirements, and reporting guidelines.
Activation Timeline and Client Release Management
The deployment schedule for the Glamsterdam upgrade follows a coordinated multi-network rollout. Following the successful activation on the Sepolia testnet at epoch 353,024 and slot 11,296,768 on October 6, 2026, attention shifts entirely to the Hoodi testnet. Hoodi will undergo its transition at epoch 132,352 and slot 4,235,264 on October 26, 2026, at 17:42:48 UTC, corresponding to a UNIX timestamp of 1793036568. At this precise activation boundary, Hoodi’s network gas limit will automatically elevate to 200 million. Mainnet activation remains unscheduled pending stable performance metrics from the testnet environments.
Node operators preparing for the Hoodi upgrade must monitor client release repositories closely. Consensus layer participants running validators must ensure that both their beacon nodes and validator clients are simultaneously updated. Tooling providers, including developers of builder middleware such as commit-boost, are also releasing compatible versions tailored for the upgrade. Operators relying on third-party block-building infrastructure should carefully review provider-specific documentation to ensure seamless compatibility with the new consensus rules.
Frequently Asked Questions
Understanding the mechanics and implications of network upgrades is vital for the broader Ethereum ecosystem. Ethereum network upgrades rely entirely on explicit opt-in cooperation from independent node operators worldwide. Client developers coordinate protocol specifications, but the actual enforcement of new rules requires validators and non-staking node operators to update their local software stacks. Nodes that fail to adopt the upgraded software will find themselves unable to follow the canonical chain after the activation threshold passes, making ecosystem-wide coordination essential for a smooth transition.
For everyday users, token holders, and participants on the Ethereum mainnet, the Hoodi upgrade requires no direct action. The current deployment schedule is strictly confined to testnet environments, and a separate advisory will be published well in advance of any mainnet transition. Similarly, non-staking Hoodi node operators only need to ensure their execution and consensus clients are updated prior to the October 26 activation timestamp. Hoodi stakers face more rigorous responsibilities, requiring them to update both beacon nodes and validator clients while familiarizing themselves with the operational requirements of enshrined proposer-builder separation and updated gas limit targets.
Application and tooling developers are encouraged to leverage the testnet rollout to audit smart contracts against new gas repricing rules, verify opcode interactions, and ensure compatibility with upcoming client interfaces. By addressing these technical adjustments early, the developer community can help ensure that the eventual mainnet deployment of Glamsterdam proceeds without disruption, further securing Ethereum’s position as a scalable, high-performance foundational settlement layer.
Ethereum & Smart Contracts
Ethereum & Smart Contracts
Ethereum & Smart Contracts
