Altcoin Lens

Network upgrades

Ethereum developers weigh a December test for Glamsterdam

Ethereum developers discussed a Hoodi testnet rehearsal for the week of December 14 as they weighed the effect of new gas rules on existing apps.

Illustration of the Ethereum diamond over a violet network of connected nodes

Ethereum developers proposed testing Glamsterdam, the network’s next upgrade, on Hoodi in the week of December 14. The November 19 execution-layer call listed December 16 and 17 as possible dates. The timing remained open after the call, and the group planned to coordinate with consensus-layer developers before making a decision.

Hoodi is a public test network. A rehearsal there would give client teams and application developers a shared environment to check how the upgrade behaves before Ethereum’s main network changes. The Ethereum Foundation postponed the previous Hoodi activation, originally scheduled for October 26, while developers investigated the gas proposals.

Where testing stands

The upgrade combines changes to how Ethereum builds blocks, tracks the data a block uses and accounts for the work transactions perform. The first testnet announcement scheduled a Sepolia rehearsal for October 6. The later Hoodi decision is a separate milestone because it gives infrastructure teams another network on which to test client releases and app behavior.

The governance discussion on November 19 was an execution-layer call. Developers discussed a December window for Hoodi and planned to coordinate with the teams responsible for Ethereum’s consensus layer before confirming it. A proposed test window can still move if client teams find that the specification or software needs more work.

Why gas is holding up the rehearsal

One of the proposals, EIP-8037, raises and separately measures the gas charged for creating state, such as adding persistent contract storage. The aim is to limit how quickly Ethereum’s stored data grows as the network makes room for more activity. The Foundation asked auditors to examine how EIP-8037 and the related EIP-8038 would interact with applications already deployed.

Some applications were written around assumptions about how much gas particular operations would use. Changing those assumptions can affect how an existing contract behaves, even when its own code stays the same. Besu’s client team argued for a narrow adjustment to the specification. Other participants favored continuing tests with the current design unless a viable alternative emerged.

Gas units measure the amount of work a transaction uses. What a user pays in ETH also depends on the price per unit of gas. The specification describes a change to the amount charged for particular operations. The November discussion offers no basis for predicting a universal change in fees or an immediate price effect for ETH.

What to watch next

The next milestones are an agreed Hoodi activation date and a decision on the gas specification to test. A successful rehearsal would give app teams evidence about compatibility and time to address findings ahead of a mainnet rollout.

For teams with contracts already deployed, the practical test is whether a routine workflow succeeds with the revised rules under realistic gas limits. Client readiness and the results of those application tests matter separately. A date for the rehearsal would make the next step concrete while leaving the mainnet schedule open.

As of November 20, the December window refers to Hoodi. A mainnet activation date remains open.

Sources