Ethereum’s scheduled Glamsterdam activation on the Sepolia testnet has passed, and two public RPC endpoints returned current blocks carrying a new block-level access-list hash field on October 7. The observations provide a concrete signal of the post-schedule block format, while Hoodi and Ethereum mainnet activation dates remain unset.
The Ethereum Foundation’s testnet announcement scheduled Sepolia for October 6, 2026, at 13:53:36 UTC, at epoch 353,024 and slot 11,296,768. Its activation table lists Hoodi and mainnet as TBD. The Sepolia milestone does not establish a mainnet launch date.
What the Sepolia block check shows
At 07:31:48 UTC on October 7, PublicNode’s Sepolia endpoint returned chain ID 0xaa36a7 and latest block 0xb4fe04, timestamped 07:31:48 UTC. At 07:32:00 UTC, 1RPC’s Sepolia endpoint returned the same chain ID and the next block, 0xb4fe05, timestamped 07:32:00 UTC.
Both responses included blockAccessListHash. EIP-7928 specifies a block_access_list_hash field in the execution block header, connecting the observed response field to Glamsterdam’s block-level access-list design.
The check used eth_chainId and eth_getBlockByNumber("latest", false). These are point-in-time observations from two named public endpoints. They do not establish the health of every client, independently verify every aspect of the fork, or constitute an Ethereum Foundation declaration that activation was successful.
The responses also showed a gas-limit field of 0xbebc200, or 200,000,000. That is the block limit, not a measurement of gas actually used. Neither this field nor the access-list hash demonstrates a performance improvement.
Glamsterdam pairs ePBS with block-level access lists
Glamsterdam combines Amsterdam on the execution layer with Gloas on the consensus layer. The Foundation identifies enshrined proposer-builder separation, or ePBS, and block-level access lists, or BALs, as headline changes.
EIP-7732 moves proposer-builder separation into consensus and separates consensus validation from execution validation. BALs record accounts and storage locations accessed during block execution, including post-execution values. EIP-7928 describes a design intended to enable parallel disk reads, transaction validation, and state-root calculation.
Those are protocol design goals, not measured results from the October 7 RPC check. Both EIP pages displayed Last Call status with a November 1, 2026 deadline when checked. They should be understood as proposals scheduled for Glamsterdam testing, rather than completed mainnet changes or final standards.
The operational call applies to Sepolia participants
The Foundation instructs Sepolia node and validator operators to update both execution and consensus clients. Validators need both a beacon node and validator client. Its announcement says no action is required from Hoodi or mainnet operators or ETH holders in response to this Sepolia testnet announcement.
Compatible client releases were available ahead of the scheduled activation. Prysm v7.2.1, released October 5, explicitly refers to the October 6 Sepolia Gloas fork at epoch 353,024. go-ethereum v1.17.7, released September 30, says v1.17.6 and v1.17.7 are ready for the Amsterdam fork on Sepolia and lists BAL and EIP-8037-related changes.
For application developers, the Foundation specifically recommends testing gas accounting and estimation because Glamsterdam includes gas-pricing and state-access changes. That is the immediate developer task identified by the official guidance, rather than an inference about token prices.
The announcement also says Sepolia builder and validator tooling compatibility guidance will be added when confirmed. Available client releases therefore should not be presented as proof that all external builder infrastructure is ready.
Mainnet timing remains an open question
The current Foundation table is the relevant boundary for the next rollout: Hoodi and mainnet are still TBD. Earlier developer discussion in All Core Developers Testing meeting #97 corroborates the Sepolia schedule but treated Hoodi as tentative.
The next material updates would be a confirmed activation schedule, official post-activation status reporting, or further tooling compatibility guidance. No official post-fork success or incident report was located in the bounded research supporting this article. Sepolia’s observed block fields do not settle those questions or guarantee mainnet outcomes.
Source check: Official documents and client release notes were checked October 7, 2026 KST. Public Sepolia RPC observations were captured October 7, 2026, from 07:31:48 to 07:32:00 UTC.
Investment responsibility notice: This article is for general information and is not investment advice. Readers are responsible for their own investment decisions.
Investment disclaimer: This article is provided for general information only and does not constitute investment, financial, legal or tax advice. Digital assets are volatile, and all investment decisions and their consequences are your own responsibility.