Ethereum Glamsterdam Upgrade: Hoodi Testnet Guide11 min read2,131 words

Ethereum Glamsterdam Upgrade: Hoodi Testnet Guide

Ethereum’s Glamsterdam upgrade reaches Hoodi on Oct. 26, 2026. Learn what ePBS, block access lists and gas changes mean—and what operators should do now.

Ethereum Glamsterdam upgradeHoodi testnetenshrined proposer-builder separationblock-level access listsEthereum gas repricing
Ethereum Glamsterdam Upgrade: Hoodi Testnet Guide

Ethereum's Glamsterdam Upgrade: What Hoodi Operators Need to Know

Ethereum's next network upgrade is going through testnets first, not mainnet. After activating on Sepolia on October 6, 2026, Glamsterdam is scheduled to activate on Hoodi at 17:42:48 UTC on October 26, 2026. For Hoodi node operators and stakers, that timing is a real deadline. For mainnet users and ETH holders, it's not a moment to switch wallets or take action.

Glamsterdam combines an execution-layer upgrade (Amsterdam) with a consensus-layer upgrade (Gloas). Its headline changes - enshrined proposer-builder separation (ePBS) and block-level access lists (BALs) - are meant to help Ethereum process more execution work while keeping validation manageable. It also updates how gas reflects execution and state growth, which could affect apps that depend on specific gas assumptions.

This guide lays out what's changing, why it matters, and what each team should do before Hoodi activation. It also keeps the "testnet work" separate from whatever happens on mainnet later. The Hoodi date is set in the announcement, but it is not being treated as a mainnet launch date.

What Glamsterdam Is and When It Activates

Glamsterdam is a coordinated Ethereum network upgrade. The execution-layer part is called Amsterdam; the consensus-layer part is called Gloas. Together, they affect how transactions get processed (execution + EVM changes) and how validators participate in agreement and block production (consensus changes).

The Hoodi activation is scheduled for epoch 132,352, slot 4,235,264, at 17:42:48 UTC on October 26, 2026. At that same epoch, Hoodi's gas limit is scheduled to rise to 200 million, matching the Sepolia gas limit. These are testnet parameters - don't treat them as a forecast for Ethereum mainnet.

Glamsterdam has already activated on Sepolia on October 6. Hoodi gives client teams, infrastructure operators, and application developers another chance to verify compatibility with the scheduled changes. As for mainnet: the activation date hasn't been decided yet. Client teams will announce it separately when they've coordinated the schedule and compatible releases.

Why a testnet activation is operationally important

A testnet upgrade isn't just a demo. It's where teams can run software against the upcoming protocol rules before those rules hit mainnet. That includes checking that clients start cleanly, that validators do their updated duties, that builder infrastructure behaves as expected, and that applications still estimate and execute transactions correctly.

Testnet won't surface every issue. Scale, transaction patterns, and infrastructure setups can differ from mainnet. Still, it's the main place to find compatibility problems before they turn into incidents on a production network. If you're responsible for production systems, that's the point: catch issues while the blast radius is smaller.

Node operators need to update both their execution-layer and consensus-layer clients before Hoodi activation. The client release tables are expected to be updated once Hoodi-compatible versions are confirmed. Use releases whose notes explicitly say they support the scheduled Glamsterdam activation on Hoodi. "It looks recent" isn't enough evidence.

The Ethereum Foundation's Hoodi announcement is the source for the activation details and release guidance. The mainnet schedule is separate from this testnet announcement.

The Protocol Changes That Matter

Glamsterdam isn't just one feature flip. It includes changes spanning block production, validation, state access, and gas accounting. The useful question isn't "is this interesting?" - it's "what should teams verify because their software depends on it?"

Enshrined proposer-builder separation

EIP-7732 brings proposer-builder separation into Ethereum's consensus protocol. In plain terms, a proposer includes a builder's commitment to an execution payload, and later the builder reveals the payload. The protocol handles payment to the proposer, reducing reliance on off-protocol coordination middleware.

It also separates consensus validation from execution validation. The stated goal is to give validators more time to validate execution payloads. A payload timeliness committee attests to whether the builder revealed the payload and whether the related blob data was available on time.

This changes responsibilities and interfaces beyond the clients themselves. If you run validators - or rely on block-building infrastructure - you should review the Glamsterdam-specific instructions before activation. If your validator setup uses external block-building services, compatibility depends on both your node versions and the tooling you're using.

That said, this isn't automatically a "you must run a builder" change for every operator. The real requirement is understanding how validator duties and any external services fit together under the new protocol. In production setups, gaps between a client upgrade and a supporting service are often where operational risk shows up.

Block-level access lists

EIP-7928 introduces enforced block-level access lists. These lists track the accounts and storage locations accessed during a block, along with post-transaction state changes. Clients can use that information to read state from disk in parallel, validate transactions in parallel, and compute state roots more efficiently.

The key detail is that the access list is defined at block level. It records the state touched across the block, rather than acting only as a per-transaction hint. The intention is to give clients a better picture of what can be coordinated concurrently.

Parallel work only helps when the protocol and client implementations can determine which tasks are safe to run in parallel. Access information doesn't remove the need to validate the resulting state correctly, and it doesn't guarantee "everything runs in parallel." The goal is to increase the amount of work clients can handle efficiently without making block validation too expensive.

Together, ePBS and BALs aim to raise execution capacity while keeping a validation model that still works for node operators. ePBS changes how payloads are proposed and revealed; BALs describe state access patterns within a block.

Gas pricing and state growth

Glamsterdam also updates gas accounting so costs track resource use more closely. EIP-8037 increases and separately meters the cost of creating state, while EIP-8038 updates state-access costs. Other changes touch intrinsic transaction gas, calldata costs, access lists, and block gas accounting.

For application teams, the practical concern is compatibility with gas behavior assumptions in contracts and tooling. If a contract assumes a fixed gas stipend, a hardcoded gas limit, or a specific amount of remaining gas, it may behave differently under the revised accounting. Gas estimation tools may also need updates to reflect the new rules.

That doesn't mean every contract breaks. The risk is mainly in code that depends on exact gas behavior rather than just completing its intended operation under the protocol's rules. Use the published Glamsterdam repricing impact guidance to identify potentially affected contracts, then test them on the upgraded testnets.

Additional execution and consensus changes

Beyond ePBS and BALs, the upgrade includes other changes listed in the announcement: ETH transfer logs, a slot-number opcode, a higher maximum contract size, a deterministic factory contract, and new stack-manipulation instructions. On the consensus side, changes include forward-compatible data structures, excluding slashed validators from proposing, and increased exit and consolidation churn.

These can matter for different teams for different reasons. A contract or EVM-tool maintainer may care about logs, opcodes, or contract-size limits. A validator operator may focus on consensus duties, exits, and consolidations. A tooling provider may need to check interfaces and assumptions across both layers.

EIP-7773 tracks the Glamsterdam upgrade. The announcement names EIP-7732, EIP-7928, EIP-8037, and EIP-8038. Check the EIP specifications and the confirmed client release notes for the exact behaviors relevant to your implementation. Don't treat the headline descriptions as the full scope.

Who Needs to Prepare - and How

What you need to do depends on whether you operate Hoodi, build applications, or just use mainnet. Treating these groups like they all share one "do it now" deadline creates work for mainnet users and leaves testnet operators underprepared.

Hoodi node operators and stakers

Before October 26, 2026, at 17:42:48 UTC, Hoodi operators should:

  1. Identify the execution-layer client and consensus-layer client used by each node.
  2. Confirm that a Hoodi-compatible release is available for both clients.
  3. Read the release notes and verify they explicitly support the scheduled Glamsterdam activation.
  4. Update both layers before activation, following the client teams' upgrade instructions.
  5. Re-check monitoring, restart procedures, and any infrastructure dependencies after the update.

Stakers should also make sure that both the Beacon Node and Validator Client are updated. Review guidance on the updated ePBS duties and any required builder or validator tooling changes. Also check how your validators set their target gas limit after activation, since Hoodi's gas limit is scheduled to move to 200 million at the activation epoch.

Don't assume updating one client updates the other. Execution-layer and consensus-layer clients are separate components, and a partial upgrade can leave a node unable to follow the upgraded network correctly. The safe approach is to verify versions and compatibility across the full setup, including any external block-building infrastructure.

Application and tooling developers

Developers should review the scheduled EIPs and test on Sepolia and Hoodi after each relevant activation. Focus on the parts of your codebase and tooling that depend on gas behavior, transaction construction, logs, opcodes, state access, or client interfaces.

A practical testing sequence looks like:

  • Look for contracts that use fixed gas stipends, hardcoded gas limits, or assumptions about remaining gas.
  • Re-run unit, integration, and transaction-estimation tests with compatible client and tooling versions.
  • Test important user flows on the upgraded testnets, especially transactions that touch multiple contracts or large state areas.
  • Check whether indexers, wallets, relayers, and monitoring tools depend on affected logs or interfaces.
  • Record any differences in gas estimates or execution behavior, then investigate before you change production assumptions.

A "works on the happy path" result isn't enough if your app uses gas-sensitive logic. Include edge cases and failure paths. If your app depends on a particular gas amount being forwarded or left available, verify that directly rather than assuming it will match older estimates.

Mainnet users and operators

For ordinary Ethereum mainnet users and ETH holders, there's no action required here. This announcement covers Hoodi, not mainnet. Mainnet wallets don't need changes just because Hoodi is upgrading, and the announcement doesn't provide a mainnet activation date.

Mainnet node operators and stakers likewise don't need to act based on the Hoodi schedule. Wait for the separate mainnet announcement, then follow the compatible client releases and timeline specified for that network. Using a testnet deadline to plan for mainnet would be a category mismatch; ignoring the later mainnet deadline would be operationally risky.

Conclusion

Glamsterdam's Hoodi activation is a testnet milestone with clear operational requirements. The ePBS and block-level access list changes reshape parts of block production and validation, and the gas repricing is a reason to double-check any gas-related assumptions in apps and tooling. The 200-million Hoodi gas limit is part of the testnet schedule, not a mainnet parameter announcement.

If you operate Hoodi, confirm compatible releases for both client layers and complete the upgrade before October 26. If you build applications or tooling, use the upgraded testnets to test the parts of your system that depend on gas, state access, logs, opcodes, or validator interfaces. If you're a mainnet user, wait for the separate mainnet announcement.

The next step is simple: identify which group you're in, then follow the schedule and guidance that apply to your network.

Frequently Asked Questions

Glamsterdam is scheduled to activate on Hoodi at epoch 132,352 and slot 4,235,264, at 17:42:48 UTC on October 26, 2026. Hoodi’s gas limit is also scheduled to rise to 200 million at that epoch.
No. This announcement covers Hoodi, not mainnet. Mainnet users and ETH holders do not need to take action based on the Hoodi activation. Ethereum’s mainnet activation date will be announced separately.
Hoodi node operators must update both their execution-layer and consensus-layer clients to releases that explicitly support the scheduled Glamsterdam activation. Stakers should update both the Beacon Node and Validator Client and review any relevant builder or validator tooling instructions.
Developers should review the scheduled EIPs and test on Sepolia and Hoodi after activation. Pay particular attention to gas accounting, fixed gas assumptions, logs, opcodes, and client interfaces. Re-run gas estimation and test application flows that depend on gas-sensitive behavior.

Related articles