Ethereum Activates Glamsterdam Upgrade on Sepolia Testnet

The activation of the Glamsterdam upgrade on the Ethereum Sepolia testnet marks a definitive pivot in the network's layer-1 scaling strategy. By fundamentally altering how blocks are proposed, built, and validated, the deployment establishes the technical foundation necessary for vast capacity increases. The upgrade went live on Sepolia on Oct. 6 at epoch 353,024, combining changes across both the execution and consensus layers ¹. As developers test the new environment, the focus remains squarely on two flagship features: enshrined proposer-builder separation and block-level access lists ¹. Together, these modifications are engineered to allow the network to handle significantly larger blocks without overwhelming validator node infrastructure ¹².

The Drive for a 200 Million Gas Limit

The most immediate structural ambition of the Glamsterdam upgrade is the facilitation of a much higher block gas limit. Before this transition, Ethereum's block gas limit hovered around 60 million ². The Glamsterdam architecture introduces the capability to push this threshold to roughly 200 million ². This aggressive expansion is visible in the network's configuration files, where the Sepolia testnet's parameters were specifically updated to mandate a 200 million gas limit starting exactly at epoch 353,024 ⁴.

Client software developers have had to adjust their tools to accommodate this new parameter. For instance, the Prysm consensus client initially released version 7.2.0, which maintained a default 60 million limit and required manual overrides from node operators to reach the 200 million target ⁵. However, the subsequent version 7.2.1 release integrated the automated schedule directly, ensuring that Prysm validators would default to the higher limit upon the fork's execution ⁵. This shift underscores a broader effort to expand baseline capacity on the primary chain, which has seen transaction costs drop considerably following earlier upgrades like Dencun and Fusaka ².

Reengineering Consensus and Execution

The Glamsterdam package is a composite of the Amsterdam execution layer update and the Gloas consensus layer update ¹. A critical component of this combination is enshrined proposer-builder separation, formally designated as EIP-7732 ¹. This protocol-level change integrates the division of labor between block proposers and block builders directly into Ethereum's consensus rules ¹. Under the new system, builders commit to an execution payload, which is then included by the proposer before the builder fully reveals the data ¹. The protocol itself now manages the financial compensation to the proposer, diminishing the historical reliance on trusted third-party middleware ¹. This structural division affords validators more time to verify execution data and introduces a timeliness committee to ensure builders reveal their payloads promptly ¹.

Parallel to these consensus shifts, the execution layer incorporates block-level access lists through EIP-7928 ¹. These lists explicitly map out the various accounts and storage slots modified during a specific block's execution, along with the resulting state changes ¹. By providing this map upfront, client software can prefetch necessary data from storage disks and process multiple transactions concurrently ¹². This parallelization is the primary mechanism that makes verifying much larger blocks feasible for everyday node operators, directly supporting the push toward higher gas limits ¹².

Overhauling Gas Economics and State Growth

Beyond throughput enhancements, Glamsterdam significantly restructures how network resources are priced. The upgrade implements comprehensive adjustments to gas accounting to more accurately reflect the true computational burden of state growth and access ¹. EIP-8037 specifically increases the cost associated with creating new state while separating its metering from standard execution costs ¹. Concurrently, EIP-8038 revises the gas fees tied to state access ¹.

These economic modifications ripple through the development ecosystem. Smart contract developers are explicitly advised to test their applications against the new pricing models on Sepolia, as contracts relying on fixed gas assumptions or hardcoded limits may face operational failures under the updated regime ¹. The changes also extend to how intrinsic transaction gas and block-wide gas are calculated, removing certain refund mechanisms via EIP-7778 ¹. When processing these updated rules, client software like Geth incorporated specific logic to account for both execution and state gas during the transaction selection phase ⁸.

Client Readiness and Security Hardening

The transition required extensive coordination among client development teams to ensure software readiness and stability. Leading up to the Oct. 6 activation, execution clients such as Geth released multiple updates to prepare for the Amsterdam fork ⁸. Geth version 1.17.7 introduced the necessary logic for the upgrade while adding features that allow node operators to customize their history pruning points ⁸.

Following the testnet activation, Geth issued version 1.17.8 on Oct. 8, prioritizing security fixes specifically related to the new Amsterdam environment ⁷. This patch addressed several denial-of-service vulnerabilities that only became active post-fork, including issues tied to block-level access lists, jump destination analysis caching, and specific peer-to-peer network handlers ⁷. The swift deployment of these security patches highlights the complexities introduced by parallel execution and state mapping.

Upgrades for Developers and Validators

Glamsterdam also ships with a suite of targeted improvements for both application builders and validator operators. For developers, the upgrade introduces native logs for fundamental ether transfers via EIP-7708, simplifying how applications track asset movements without relying on wrapped tokens ¹. It also delivers a new opcode for querying slot numbers, deterministic factory contracts, and an increased maximum size for smart contracts ¹.

Validators face a new operational landscape. Beyond the duties introduced by proposer-builder separation, the consensus layer now enforces forward-compatible data structures and actively prevents validators who have been slashed from proposing new blocks ¹. The upgrade also adjusts validator churn limits to manage network entry and exit more efficiently ¹. Node operators using client infrastructure must ensure both their execution and consensus layers are updated, as failing to support the new rules results in a loss of network synchronization ¹. Ethereum Schedules Glamsterdam Upgrade for Sepolia Activation on Oct. 6 previously outlined the critical necessity of these simultaneous client updates.

Implications for Ethereum's L1 Trajectory

The successful deployment of these features on Sepolia reinforces Ethereum's evolving strategy regarding base-layer utilization. Historically, the prevailing wisdom assumed that the primary network would remain perpetually expensive, pushing most decentralized applications toward layer-2 scaling solutions ². However, the combination of dedicated blob space from earlier upgrades and the massive capacity expansions tested in Glamsterdam suggests a paradigm where the base chain becomes viable for a broader range of activities ².

By driving execution costs down and block limits up, Ethereum is positioning its primary chain to reclaim activity that benefits from shared liquidity and the strongest possible security guarantees ². While layer-2 networks remain critical for extremely high-volume or zero-cost transactions, the Glamsterdam architecture ensures that the base layer does not become an exclusive settlement layer strictly reserved for rollups ².

What to Watch

The immediate focus shifts to how the upgraded testnet performs under sustained load with the 200 million gas limit. Developers will monitor the network for consensus stability and client performance, particularly tracking how effectively block-level access lists facilitate parallel processing without causing state bloat. Client software teams will continue to patch any emerging vulnerabilities, mirroring the rapid response seen with Geth's post-activation releases ⁷.

Looking further ahead, the activation dates for the subsequent Hoodi testnet and the Ethereum mainnet remain undetermined ¹. The success and stability of the Sepolia deployment will heavily influence these timelines. Beyond Glamsterdam, the developer community is already outlining the contours of the next named upgrade, Hegotá ². That future package is expected to focus on native account abstraction and inclusion lists, continuing the structural overhaul initiated by the current testnet phase ².