Ethereum readies Glamsterdam for October 6 Sepolia test

Ethereum is scheduled to activate the Glamsterdam upgrade on the Sepolia testnet at 13:53:36 UTC on October 6, moving its next major protocol package from short-lived development networks onto a long-running public test environment.

As of Coinburn’s October 5 publication window, the activation has not happened. The Ethereum Foundation’s current schedule places the fork at epoch 353,024 and slot 11,296,768, while leaving both Hoodi and mainnet dates undecided. The distinction matters: tomorrow’s event can expose software and application failures under realistic conditions, but it will not change Ethereum mainnet.

The immediate deadline falls on Sepolia operators. They must update both their execution client and consensus client before the activation point. The Foundation’s current compatibility table lists releases across the major client families, and Geth’s September 30 release notes confirm that versions 1.17.6 and 1.17.7 are ready for Sepolia’s Amsterdam fork.

Block building moves into the protocol

Glamsterdam combines the Amsterdam execution-layer changes with the Gloas consensus-layer changes. Its headline feature, enshrined proposer-builder separation, moves the exchange between block proposers and specialized builders into Ethereum’s consensus rules.

Under that design, a proposer includes a builder’s commitment, the builder later reveals the execution payload, and the protocol handles payment to the proposer. A payload-timeliness committee checks whether the payload and associated blob data arrived when required. The goal is to reduce reliance on trusted middleware for builder payments and give validators more time to verify execution payloads.

That is an architectural change, not a demonstrated performance result. Sepolia’s activation will test client interoperability and operational behavior; it cannot by itself prove that mainnet will gain a particular throughput level or that external builder infrastructure will work without disruption.

Access lists and gas rules widen the test

A second major feature requires each block to carry a block-level access list recording the accounts and storage locations it touched, along with post-transaction state changes. Ethereum’s specification says these lists can let clients read state and validate parts of transaction processing in parallel.

The package also reprices state creation, state access, transaction overhead and other operations. That makes the test relevant beyond validator software. Wallets, indexers, gas estimators and smart-contract developers may have embedded assumptions about fixed gas stipends, maximum gas limits or remaining gas during execution.

Chainlink’s developer documentation warns that workflows with hardcoded gas limits may need extra headroom or no fixed limit, and advises testing them on Sepolia after activation. Its warning applies specifically to affected workflows; it does not establish that every application will fail. The correct measurement comes after the fork, when developers can compare transaction success and gas use under the new rules.

What tomorrow can establish

A clean Sepolia activation would show that upgraded clients can follow the new rules on a persistent public testnet. It would also open a wider observation window for application compatibility, builder duties, payload availability and changed gas accounting.

It would not schedule mainnet. The Foundation explicitly says this announcement covers Sepolia only, and the Glamsterdam meta specification still leaves Hoodi and mainnet activation fields blank. It also would not demonstrate production adoption, economic benefit or security under mainnet load.

That limitation is why the October 6 checkpoint matters now without being treated as a launch. Ethereum’s earlier Glamsterdam devnets established development progress; Sepolia is a separate operational milestone. The follow-up questions are whether the network finalizes normally, whether client teams report divergence or bugs, and whether downstream applications uncover gas-estimation or block-building failures before developers set the next public-testnet date.