Glamsterdam Keeps Its 6 October Sepolia Test

Ethereum developers have a date for the next public test of the Glamsterdam upgrade, and they restated it on 1 October rather than moving it. The schedule to remember is Ethereum Glamsterdam Sepolia October 6 2026: Sepolia activation at epoch 353,024, slot 11,296,768, at 4:53:36 p.m. Moscow time, which is 13:53:36 UTC. Hoodi and the main network are not on that same footing. The original announcement is slightly older than a 48-hour window.

The developer call on 1 October reconfirmed the Sepolia time. That gap should be said plainly.

What happened

The Ethereum Foundation's testnet post names the Sepolia activation in the chain's own clock. Ethereum time is divided into slots, and slots are grouped into epochs. The post picks epoch 353,024 and slot 11,296,768, and it picks a wall-clock time of 13:53:36 UTC on 6 October 2026. In Moscow that is 4:53:36 p.m. The page is dated 28 September 2026 in the body.

Hoodi, a second test network, is marked TBD. Mainnet, the network that holds real value, is marked TBD as well.

A test network is a public copy of the system used to try an upgrade before anyone depends on it for real balances. Sepolia and Hoodi are those copies in this plan. Hitting an epoch and a slot on Sepolia does not move mainnet.

It tells developers whether the software they intend to ship behaves as expected on a live, public test chain. The foundation post is the document that first set the Sepolia coordinates now being repeated.

EtherWorld's recap of the developer call ACDC #188, published on 1 October, says the room kept the 6 October Sepolia target. The time it records is 13:53 UTC, which is 4:53 p.m. in Moscow, the same minute as the foundation's 13:53:36 UTC. Hoodi, on that recap, is tentative: 27 October, if Sepolia goes well. Mainnet is not scheduled.

The call did not convert the foundation's TBD into a mainnet date. It added a conditional date for Hoodi and left the main network unscheduled.

The foundation post sits slightly outside a strict 48-hour news window. The body date is 28 September, and the announcement itself is a little older than that window. What is inside the window is the reconfirmation. On 1 October the developers kept the Sepolia target instead of slipping it.

The original post is the foundation's testnet announcement. The reconfirmation is EtherWorld's ACDC #188 recap.

Why it matters

Glamsterdam is a protocol upgrade, a coordinated change to the software nodes run. Upgrades of that kind are rehearsed on testnets because a mistake on mainnet is a mistake in the system people actually use. Sepolia is the rehearsal with a clock attached. Epoch, slot, and a UTC timestamp are how Ethereum makes "6 October" unambiguous.

Two clients that disagree about the slot would not be activating the same upgrade. Publishing the numbers is the point of the foundation post.

The 1 October call matters because testnet dates slip. A date that is merely printed in September and never mentioned again is a weaker fact than a date a developer call has just kept. EtherWorld's recap says they kept it, at 13:53 UTC on 6 October. The seconds in the foundation post, 13:53:36 UTC, are the finer figure.

The call's minute and the post's minute agree. This article does not treat the missing seconds in the recap as a conflict. It treats them as two reports of the same scheduled minute, one of them more precise.

Hoodi's status is the part readers most often flatten. On the foundation page it is TBD. On the 1 October recap it is 27 October, tentative, and only if Sepolia goes well. A tentative date with a condition is not a promise.

If Sepolia does not go well, the condition fails, and the 27 October mark has no force even as a hope the call was willing to state. Mainnet is simpler. It is not scheduled. TBD on the foundation page and "not scheduled" in the recap are the same message.

The age of the original announcement is part of the honesty of the story. A news report that pretends the foundation post was published inside the last two days would be wrong. The page is dated 28 September in the body, and the announcement is slightly older than a 48-hour window. The fresh fact is the reconfirmation on 1 October.

Both belong in the lede. One without the other is a distortion.

For related Ethereum and protocol context, see the EIP-8363 scope change and Hyperliquid's MiCA position.

What's next

Sepolia is the step with a hard coordinate: 6 October 2026, 13:53:36 UTC, 4:53:36 p.m. Moscow time, epoch 353,024, slot 11,296,768. That is the activation the foundation scheduled and the call kept. What happens on that testnet is the evidence the Hoodi condition refers to. Hoodi is penciled for 27 October only if Sepolia goes well, and only in the tentative sense EtherWorld recorded.

Mainnet has no date. The foundation left it TBD. The call did not fill the blank.

Anyone looking for a day when Glamsterdam reaches the network that holds real balances will not find it in these two documents. The schedule that exists is a test schedule.

The clean way to hold the story is chronological. An announcement slightly older than 48 hours, with a body date of 28 September, set Sepolia and left Hoodi and mainnet open. On 1 October, developers reconfirmed Sepolia at the same hour and added a conditional, tentative Hoodi date of 27 October.

They did not schedule mainnet. That is the whole of the update.