Prysm 7.2.1 Sets 200M Gas Default for Glamsterdam

| unchainedcrypto.com
Ethereum consensus client Prysm released version 7.2.1 before the Glamsterdam upgrade on the Sepolia testnet. The update makes the 200 million gas limit the default for Prysm validators after the fork, replacing the previous 60 million default that required manual configuration. Glamsterdam is scheduled for Sepolia epoch 353,024, at 13:53:36 UTC on 6 October 2026. The higher gas limit, introduced under EIP-8261, could allow more transactions and on-chain operations per block, but it will also increase hardware and execution-node performance demands. Prysm 7.2.1 enables partial data columns by default and fixes an issue involving construction of the first post-fork block. Older command-line settings can still override the new limit, although Prysm now displays a startup warning. Teku continues to use a 60 million gas default and requires operators to set 200 million manually. Glamsterdam combines the Gloas consensus-layer and Amsterdam execution-layer upgrades, including enshrined proposer-builder separation and block-level access lists. Hoodi and Ethereum mainnet activation dates remain undecided. For traders, Prysm and Glamsterdam are important Ethereum infrastructure developments, but the testnet rollout does not directly alter ETH market conditions. The immediate price impact is therefore likely to be limited.
Neutral
The news is neutral for ETH because Glamsterdam remains a Sepolia testnet event and Ethereum mainnet activation has not been scheduled. In the short term, the Prysm release may support confidence among developers and node operators by reducing configuration errors and improving fork readiness, but it does not change ETH supply, demand, fees or trading access on mainnet. Traders may briefly react to successful testing or reports of client problems, creating limited volatility around the activation time. Over the longer term, a successful 200 million gas test could support Ethereum’s scaling capacity and improve sentiment toward the network. However, higher block capacity also raises hardware, execution and decentralisation risks. The need for manual configuration in Teku and the absence of confirmed mainnet dates add uncertainty. These factors make a sustained ETH price move unlikely until the upgrade progresses toward mainnet deployment.