Ethereum's Glamsterdam Hits Hoodi on October 26 With a 200M Gas Limit

So when does Glamsterdam actually change anything for people who use Ethereum? Not on October 26. That's the date developers just pinned to the Hoodi test network, and it's a date worth writing down anyway.

Activation lands at epoch 132,352, slot 4,235,264, which works out to 17:42:48 UTC. At that exact moment the Hoodi gas limit climbs to 200 million. Mainnet, for the record, still has no activation date at all. Nobody's shipping this to the chain that holds your money until the test networks stop surprising people.

The raw numbers

Two testnets are now on the clock. Sepolia took the upgrade on October 6. Hoodi follows twenty days later, on October 26 at 17:42:48 UTC, and it's the last real dress rehearsal before developers pick a mainnet slot.

Then there's the 200 million gas limit. Mainnet block gas limits have been crawling up through the 30s and 40s of millions over the past year, so Hoodi at 200 million is roughly four to five times the throughput Ethereum handles today on its production chain. That's not a coincidence, and it's not a promise either. It's a stress test dressed up as a configuration change.

Here's what a 200 million gas limit actually tests. It tests whether execution clients can keep up with state writes at that rate. It tests whether consensus clients can gossip blocks that big without blowing past slot deadlines. It tests whether the state growth curve stays somewhere near tolerable when you quadruple the amount of work per block. Throughput is table stakes now. The real bottleneck is whether the stack holds together when you push it.

Validators and node operators on Hoodi need compatible execution and consensus clients installed before 17:42:48 UTC on October 26. Miss that window and your node falls off the network. That's the unglamorous part of every hard fork, and it's the part that breaks things in practice.

What's actually in the box

Two structural changes sit at the center of Glamsterdam, and neither one is the gas number everyone's quoting.

The first is enshrined proposer-builder separation, ePBS. Today, builders and proposers find each other through relays sitting outside the protocol, which means a handful of off-chain services carry a trust assumption that Ethereum's base layer never agreed to. ePBS moves that auction into the protocol itself. Builders commit to a block, a committee of validators attests to whether the payload actually showed up on time, and the relay's role shrinks from indispensable middleman to convenience layer. That's a real reduction in protocol risk, and it's the most consequential thing in this upgrade by a wide margin.

The second is block-level access lists. Short version: they let clients figure out, ahead of execution, which parts of a block touch which parts of state, so they can validate work in parallel instead of single file. That's a throughput play, but it's also a data play, because access lists mean more bytes per block moving across the network. Every parallelism win on the execution side costs something on the propagation side. That tradeoff is the whole game.

And then there's the gas accounting rework, including how Ethereum charges for creating and accessing state. This one's boring in a headline and brutal in production. Application developers who hardcoded gas assumptions into contracts, deployment scripts, or fee estimators are about to find out how many of those assumptions were wrong. My honest take: the repricing will break more tooling than anyone's currently budgeting for, and most of that breakage will show up quietly, in reverts and out-of-gas errors, weeks after mainnet activation.

Let's talk blob economics for a second. Glamsterdam isn't a blob capacity upgrade the way the Fusaka line of work is. It's a block production and execution cost upgrade. But the two are tightly coupled, because ePBS changes who gets to assemble blocks and how much they can pack into them, and that shapes how rollups bid for space. If you're running an L2, the builder auction mechanics in ePBS matter to your cost structure more than the headline gas limit does.

What builders and node operators are saying

The people who actually have to run this software aren't celebrating the 200 million figure. According to the Ethereum Foundation's activation notice, Hoodi is meant to give developers one more environment to check compatibility before a mainnet date gets chosen, and that framing is telling. Test networks exist to find failures, and a 200 million gas limit is an invitation for failures to show up.

Client teams are watching slot timing. If blocks start arriving late at 200 million gas, you'll see it in missed attestations and slower finality, and you'll see it in the first twelve hours, not the first twelve days. Builders are watching the ePBS auction mechanics, because moving an auction from an off-protocol relay into consensus changes the timing constraints they operate under. And node operators are watching disk. State growth is the quiet killer of home staking, and every gas limit increase pushes that curve steeper.

Does anyone actually need 200 million gas per block on a testnet? No. And that's exactly why it's useful.

What to watch

Three concrete things, in order of how much they'll tell you.

First, the client releases. Watch for compatible execution and consensus client versions shipping for Hoodi operators with enough lead time before October 26. Late client releases are the single best predictor of a messy mainnet fork, and the Sepolia run on October 6 gives developers a reference point for how much lead time is enough.

Second, Hoodi's first 48 hours. Look at missed slots, attestation inclusion rates, and whether the network keeps finalizing smoothly while running four to five times mainnet's throughput. If Hoodi sails through at 200 million gas without drama, the case for a mainnet gas limit increase gets much stronger, and the case for scheduling Glamsterdam on mainnet gets easier to make on the next All Core Devs call.

Third, the mainnet date itself. Developers won't pick one until Hoodi has run clean for a stretch. Historically that gap has been measured in weeks, not days, so a plausible mainnet window puts activation sometime in the following quarter, with the exact slot chosen at a later coordination call. Watch the ACD agenda rather than the price chart. The scaling roadmap just got more interesting, and the calendar is the signal.

The thing worth internalizing: Glamsterdam isn't a capacity upgrade you'll notice in your fees. It's a plumbing upgrade. ePBS changes who builds blocks and under what rules, access lists change how fast clients can validate them, and repriced gas changes what your contracts can afford to do. Nobody cares about infrastructure until it breaks. The point of October 26 is to make sure it breaks on Hoodi first.