Glamsterdam Activates on Sepolia: Ethereum Upgrade Enters Live Testing, Mainnet Date Still Unannounced
Latest update (October 6, 2026): Glamsterdam was scheduled to activate on Sepolia at 13:53:36 UTC. The Ethereum Foundation’s official schedule lists epoch 353,024 and slot 11,296,768. In this round of checks, the target slot returned a `gloas` block version from the PublicNode Sepolia Beacon API, and slot 11,297,013 also had a `gloas` block, indicating that the activation point had been reached and the chain continued producing blocks. Cointelegraph also reported that Glamsterdam had gone live on Sepolia that day. Note: this is a testnet, not an Ethereum mainnet upgrade; dates for Hoodi and mainnet are still to be determined.
My assessment: This moves the upgrade from “schedule confirmed” to “testnet execution,” shifting the focus of validation from node readiness to client compatibility, continued chain operation, and post-upgrade behavior. Glamsterdam comprises the execution-layer Amsterdam and consensus-layer Gloas, with key areas including enshrined proposer-builder separation (ePBS) and block-level access lists (BAL). However, activation on a single testnet does not prove that mainnet upgrade risks have been eliminated, nor can it directly establish that lower fees or higher throughput have been delivered.
The main transmission channel to the crypto market is $ETH : steady testing progress may reduce uncertainty around the upgrade timeline and affect developers’ and validators’ confidence in Ethereum’s roadmap. Short-term prices are still shaped by overall risk appetite, capital flows, and macroeconomic conditions. At the time of this round’s Binance Spot `/api/v3/ticker/24hr` query (2026-10-06 14:41:26 UTC), ETHUSDT spot rolling 24-hour quoteVolume was approximately 642 million USDT. This only indicates the trading volume of that spot pair at the time; it does not represent incremental buying caused by the upgrade or indicate a price direction.
Suggested response: Ordinary holders do not need to migrate assets, change wallets, or adjust their mainnet operations because of Sepolia’s activation. Do not mistake testnet success for a mainnet upgrade. Node and infrastructure operators should follow the official client compatibility list, verify execution-layer and consensus-layer client combinations, synchronization, and block production in a test environment, and then schedule maintenance windows in line with Hoodi and mainnet announcements.
Going forward, monitor post-upgrade client compatibility and chain stability on Sepolia, Hoodi’s activation time, the mainnet upgrade scope and date, and whether ePBS/BAL implementations proceed as planned. If persistent forks, client compatibility failures, delays to Hoodi testing, or changes to the mainnet plan occur, the assessment that “the upgrade is progressing on its current schedule” should be revised downward. Only if subsequent testing remains stable and a clear mainnet schedule is announced will there be a basis for further assessing potential network impacts.
Sources: Ethereum Foundation, “Glamsterdam Testnet Announcement” (Sepolia activation schedule): https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement
On-chain verification: PublicNode Ethereum Sepolia Beacon API, slots 11,296,768 (activation point) and 11,297,013, queried at 2026-10-06 14:43 UTC; response summary saved in this round’s report directory.
Progress report: Cointelegraph, 2026-10-06: https://cointelegraph.com/news/ethereums-glamsterdam-upgrade-launches-on-sepolia-testnet
Market data source: Binance Spot public REST API `/api/v3/ticker/24hr`, ETHUSDT spot rolling 24-hour quoteVolume, queried at 2026-10-06 14:41:26 UTC; full snapshot is in this round’s report directory. This is personal analysis and does not constitute investment advice.
Latest update (October 6, 2026): Glamsterdam was scheduled to activate on Sepolia at 13:53:36 UTC. The Ethereum Foundation’s official schedule lists epoch 353,024 and slot 11,296,768. In this round of checks, the target slot returned a `gloas` block version from the PublicNode Sepolia Beacon API, and slot 11,297,013 also had a `gloas` block, indicating that the activation point had been reached and the chain continued producing blocks. Cointelegraph also reported that Glamsterdam had gone live on Sepolia that day. Note: this is a testnet, not an Ethereum mainnet upgrade; dates for Hoodi and mainnet are still to be determined.
My assessment: This moves the upgrade from “schedule confirmed” to “testnet execution,” shifting the focus of validation from node readiness to client compatibility, continued chain operation, and post-upgrade behavior. Glamsterdam comprises the execution-layer Amsterdam and consensus-layer Gloas, with key areas including enshrined proposer-builder separation (ePBS) and block-level access lists (BAL). However, activation on a single testnet does not prove that mainnet upgrade risks have been eliminated, nor can it directly establish that lower fees or higher throughput have been delivered.
The main transmission channel to the crypto market is $ETH : steady testing progress may reduce uncertainty around the upgrade timeline and affect developers’ and validators’ confidence in Ethereum’s roadmap. Short-term prices are still shaped by overall risk appetite, capital flows, and macroeconomic conditions. At the time of this round’s Binance Spot `/api/v3/ticker/24hr` query (2026-10-06 14:41:26 UTC), ETHUSDT spot rolling 24-hour quoteVolume was approximately 642 million USDT. This only indicates the trading volume of that spot pair at the time; it does not represent incremental buying caused by the upgrade or indicate a price direction.
Suggested response: Ordinary holders do not need to migrate assets, change wallets, or adjust their mainnet operations because of Sepolia’s activation. Do not mistake testnet success for a mainnet upgrade. Node and infrastructure operators should follow the official client compatibility list, verify execution-layer and consensus-layer client combinations, synchronization, and block production in a test environment, and then schedule maintenance windows in line with Hoodi and mainnet announcements.
Going forward, monitor post-upgrade client compatibility and chain stability on Sepolia, Hoodi’s activation time, the mainnet upgrade scope and date, and whether ePBS/BAL implementations proceed as planned. If persistent forks, client compatibility failures, delays to Hoodi testing, or changes to the mainnet plan occur, the assessment that “the upgrade is progressing on its current schedule” should be revised downward. Only if subsequent testing remains stable and a clear mainnet schedule is announced will there be a basis for further assessing potential network impacts.
Sources: Ethereum Foundation, “Glamsterdam Testnet Announcement” (Sepolia activation schedule): https://blog.ethereum.org/2026/09/17/glamsterdam-testnet-announcement
On-chain verification: PublicNode Ethereum Sepolia Beacon API, slots 11,296,768 (activation point) and 11,297,013, queried at 2026-10-06 14:43 UTC; response summary saved in this round’s report directory.
Progress report: Cointelegraph, 2026-10-06: https://cointelegraph.com/news/ethereums-glamsterdam-upgrade-launches-on-sepolia-testnet
Market data source: Binance Spot public REST API `/api/v3/ticker/24hr`, ETHUSDT spot rolling 24-hour quoteVolume, queried at 2026-10-06 14:41:26 UTC; full snapshot is in this round’s report directory. This is personal analysis and does not constitute investment advice.