Ethereum’s Next Scaling Rehearsal Puts Gas Assumptions on Trial.

A larger engine still needs a road test. For Ethereum’s Glamsterdam upgrade, the next one now has a date—and a reason for developers to reopen assumptions buried in their code.

The Ethereum Foundation’s October 16 announcement schedules Glamsterdam on the Hoodi testnet for October 26 at 17:42:48 UTC. Ether ($ETH) holders and mainnet operators have no action to take from this announcement. A mainnet activation date remains undecided.

The immediate story is preparation: a test network gets more execution capacity while applications face a changing gas rulebook.

The Hoodi Glamsterdam schedule

The merged Hoodi configuration change, merged October 9, sets epoch 132,352, slot 4,235,264 and timestamp 1793036568. It also schedules a 200 million gas limit at that epoch. These values match the later Foundation notice.

Blockchain News reported the Hoodi schedule on October 16, including the activation time and continued absence of a mainnet date. Panther checked the underlying announcement and configuration rather than relying on that report’s client list.

Hoodi operators need compatible execution and consensus clients before activation. Validators must also update their beacon node and validator client. The Foundation’s release table is being filled as support is confirmed; an empty entry is not a compatible-version recommendation.

A bigger block budget changes the engineering problem

The 200M figure measures the scheduled block gas limit on Hoodi. It is not 200 million transactions, a measured throughput result or a promise about transaction fees on mainnet.

One building block is EIP-7928’s block-level access lists. They record the accounts and storage locations a block touches, alongside resulting state changes. That information lets clients organize disk reads and validation in parallel instead of discovering every dependency as execution unfolds.

Glamsterdam also brings proposer-builder separation into the consensus protocol. The Foundation describes a process in which a proposer includes a builder’s commitment and the builder later reveals the payload. The intended benefit is less reliance on trusted middleware for that exchange.

These are mechanisms to test. A higher configured limit alone does not demonstrate that every client, tool and application handles the new workload well.

The gas assumptions worth testing now

The Foundation’s August repricing impact guide supplies the practical warning behind the new deadline. Its historical transaction replays found most contracts unaffected, but a smaller group depends on gas assumptions that the new rules change.

Examples include fixed stipends, hardcoded call limits, logic branching on remaining gas and presigned transactions with fixed limits. Some failures can be resolved by supplying more gas; others need changes to the affected code path. The guide also tells wallet and infrastructure developers to update gas estimation rather than reuse cached constants.

For builders, the useful work is specific: identify those assumptions, reproduce the relevant transaction flows under the new schedule and test the proposed fix. The Foundation’s current notice directs testing on Sepolia and on Hoodi after activation.

For readers watching network metrics, keep configuration separate from observed demand. Panther explored a related measurement problem in its Solana transaction-count analysis: protocol changes can alter what a headline number means.

Panther Takeaway

Treat October 26 as a rehearsal deadline for the people running and building on Hoodi. The valuable result will be evidence that software behaves correctly under the new rules. Mainnet timing, real-world throughput and future fees require their own evidence.

Sources and verification

• Ethereum Foundation, October 16: activation, operator guidance and mainnet status.
• Hoodi configuration PR #31: merged schedule and gas-limit settings.
• EIP-7928: access-list design and intended validation benefits.
• Foundation repricing guide, August 24: contract risk categories and developer testing guidance.
• Blockchain News, October 16: independent coverage corroborating the schedule.

PANTHER JOURNAL #030. Checked October 18, 2026. Scheduled testnet activation; no claim of completed activation or a confirmed mainnet date.