October 6, 2026 — The Ethereum Glamsterdam upgrade is scheduled to reach the Sepolia testnet today, giving developers a public testing environment for changes to block production, validation and execution capacity. Activation is set for 13:53:36 UTC, at epoch 353,024.
The milestone moves Ethereum’s scaling work into another testing phase. Its importance lies in whether clients, validators and applications handle the new rules reliably—not simply whether the scheduled fork boundary is reached.
Glamsterdam combines Amsterdam, the execution-layer upgrade, with Gloas, the consensus-layer upgrade. Together, they change how Ethereum constructs and verifies blocks while addressing the resource costs of a growing network.
Ethereum Glamsterdam upgrade: the confirmed Sepolia schedule
Item | Scheduled detail |
Network | Sepolia testnet |
Activation date | October 6, 2026 |
UTC time | 13:53:36 |
India time | 7:23:36 PM IST |
Activation epoch | 353,024 |
Starting slot | 11,296,768 |
Hoodi activation | Not yet confirmed |
Mainnet activation | Not yet confirmed |
The deployment schedule confirms Sepolia’s fork parameters. It does not establish that activation has completed successfully or set a mainnet launch date.
ePBS changes the relationship between proposers and builders
Enshrined proposer-builder separation, or ePBS, brings the exchange between block proposers and builders into Ethereum’s protocol.
Builders assemble execution payloads containing transactions. Proposers select commitments to those payloads for inclusion in consensus blocks. Under EIP-7732, the builder subsequently reveals the committed payload, while the protocol provides a mechanism for payment to the proposer.
A Payload Timeliness Committee checks whether the payload was revealed on time and whether the associated blob data was available. Execution validation is separated from the immediate consensus-validation task, giving validators a different timetable for processing the block.
The practical objective is to reduce reliance on trusted middleware for the proposer-builder exchange and ease a bottleneck in block validation. That is an architectural change; it does not, by itself, guarantee a particular transaction rate or eliminate every form of MEV.
Access lists help clients process work in parallel
The second headline feature is block-level access lists, introduced through EIP-7928.
These lists record the accounts and storage locations accessed during a block, alongside changes to their values. Providing that information helps clients identify transaction dependencies and organise parallel work.
The specification supports parallel disk reads, transaction validation and state-root calculation. In plain terms, clients gain a clearer map of the data a block touches before completing all the associated processing.
This creates opportunities for more efficient execution. Actual performance still depends on client implementations, hardware and the transactions being processed.
Higher gas limits need careful interpretation
Sepolia’s configuration includes a 200 million gas-limit schedule at the fork, but client settings deserve attention.
Prysm’s v7.2.0 release notes explain that the schedule landed after that release was cut. Validators using it therefore default to 60 million gas in their Gloas proposer preferences unless they explicitly configure a higher value.
The release also warns that the older --suggested-gas-limit option has no effect after Gloas. Operators need to follow the updated proposer-settings or keymanager instructions.
These are testnet configuration details. They should not be presented as evidence that Ethereum mainnet has already adopted the same capacity.
Glamsterdam also changes how state creation is charged. EIP-8037 separates aspects of state-growth accounting and reprices the creation of permanent data, addressing the storage burden that accompanies scaling.
What operators, developers and ETH holders should do
Sepolia node operators must run execution and consensus clients supporting the scheduled fork. Validator operators also need compatible beacon-node and validator-client software, along with updated builder tooling where applicable.
Application developers should test gas estimation and contracts that depend on fixed gas assumptions. The upgrade changes accounting rules as well as block infrastructure.
Mainnet ETH holders have no action to take for this Sepolia event. Mainnet and Hoodi instructions will be issued separately when their schedules are confirmed.
Bitnxt view: the useful result is reliable operation after the fork
Bitnxt’s editorial assessment: Sepolia’s value is the evidence it produces. Sustained finality, consistent behaviour across clients, dependable payload delivery and application compatibility will matter more than an announcement that the activation epoch has arrived.
The broader technical direction connects with Bitnxt’s coverage of Vitalik Buterin’s Ethereum architecture vision. Readers exploring separate transaction-design proposals can also revisit EIP-8141 and Ethereum’s frame transactions; that proposal is distinct from today’s Sepolia fork.
Ethereum’s roadmap lists Q4 2026 as the expected mainnet window, with the date still unconfirmed. Successful testnet operation would strengthen readiness, while issues discovered during testing could require further work before deployment.
