Ethereum Client Prysm Ships 200M Gas Limit Fix Hours Before Glamsterdam Test
Prysm’s new release automatically adopts Sepolia’s 200 M gas limit just before Glamsterdam activates, whereas Teku remains on the old 60 M default.

Prysm’s 200 M Gas‑Limit Fix Arrives Just in Time for Sepolia’s Glamsterdam Upgrade
Ethereum’s test‑net Sepolia is set to receive a major protocol change known as Glamsterdam. The upgrade, scheduled for epoch 353,024 (13:53:36 UTC on Oct 6), will raise the network’s gas limit from 60 million to 200 million. In a race against time, the Prysm team released version 7.2.1 hours before the fork activates, ensuring that validators no longer need to tweak settings manually.
Why the gas‑limit matters
Gas is the unit that measures the computational effort required to execute transactions on Ethereum. A higher gas limit allows more transactions per block, which can increase throughput and reduce congestion. However, it also demands more resources from node operators, as each block can contain more data. The jump from 60 million to 200 million is more than triple the previous default, a change that could significantly alter the economics of running a validator on Sepolia.
Prysm’s timely update
Prysm’s v7.2.1, released by Offchain Labs, automatically sets the 200 million limit once Glamsterdam activates. The release notes state that the change “needs no action” for operators, and the client now warns if a legacy gas‑limit flag is still present. This contrasts with the earlier v7.2.0, which required validators to manually set the flag to match the new network configuration.
The update also enables partial data columns by default, allowing nodes to trade individual cells of blob data instead of entire columns—a feature that can reduce bandwidth usage. Additionally, a bug that affected the construction of the first post‑fork block in certain scenarios has been patched.
Teku still sticks to the old default
While Prysm has aligned with the new schedule, the other major consensus client, Teku, remains on the 60 million default. Teku 26.9.1, the latest release as of Tuesday morning, continues to require a command‑line flag to raise the gas limit to 200 million. This divergence means that operators running Teku will need to manually update their configuration if they wish to participate fully in Glamsterdam.
What this means for the community
The close timing of Prysm’s patch underscores the importance of keeping client software up to date, especially when protocol upgrades involve critical configuration changes. Operators who rely on the default settings can now rest assured that Prysm will automatically adapt to Sepolia’s new gas limit, while those on Teku should take action to avoid potential misconfigurations.
For developers and validators, the upgrade presents an opportunity to test the network’s new capacity and to evaluate the impact of higher gas limits on performance and cost. As the Ethereum Foundation continues to refine the Glamsterdam schedule, the community will watch closely to see how these changes influence the broader ecosystem.
Takeaway
Prysm’s quick release ensures that validators on Sepolia can seamlessly adopt the 200 million gas limit, while Teku users must still manually adjust their settings. The upgrade highlights the dynamic nature of Ethereum’s test‑net ecosystem and the need for vigilant client maintenance.
---
TL;DR: Prysm’s v7.2.1 automatically sets Sepolia’s new 200 million gas limit just before Glamsterdam activates, while Teku still requires manual configuration to match the upgrade.
Source
Read original sourceWhy we picked this
Official protocol update on Prysm gas limit fix, relevant to operators and protocol governance.