Prysm 7.2 schedules Gloas on Sepolia but proposes at 60M gas, not 200M
Victoria Shinder1 min readPrysm v7.2.0, published on 28 September, schedules the Gloas fork on the Sepolia testnet at epoch 353024, on 6 October 2026 at 13:53:36 UTC. Sepolia operators must update before the fork and must also run an execution client that supports the matching Amsterdam fork. Gloas is not yet scheduled on Hoodi or mainnet.
The release notes flag one trap. The Sepolia Gloas configuration published upstream on 24 September adds an EIP-8261 gas limit schedule that raises the network's gas limit to 200 million at the fork. That entry landed after v7.2.0 was cut, so validators on this release default to 60 million in their Gloas proposer preferences. Those who want to propose at 200 million must set it explicitly: "gas_limit": "200000000" in a version 2 proposer settings file, or through the keymanager API at POST /eth/v1/validator/{pubkey}/gas_limit. The old --suggested-gas-limit flag only applies to pre-Gloas mev-boost registrations and does nothing after the fork. A follow-up release will include the schedule.
The release also brings validator-client support for Gloas builders and deprecates --with-builder, --enable-builder and --suggested-gas-limit. Proposer settings files now reject unknown keys, so operators should review theirs before updating. Other changes include an active-active REST mode that picks the best connected beacon node, the fast confirmation rule behind --enable-fast-confirmation, and NodeOps bootnodes replacing the Ethereum Foundation's for mainnet, Sepolia and Hoodi.
Why it matters
A testnet fork is where client teams find out whether their defaults agree. Here the release itself says they will not agree on day one: Prysm proposers who do nothing will build smaller blocks than the network allows. On a testnet that is a measurement problem; the point of flagging it now is that it must not reach mainnet.