Upgrade Watch: Glamsterdam Devnet 7 Nears Final Launch

Once the network goes live, the protocol enters a mild specification freeze: structural changes stop, minor parameter adjustments remain possible. For smart contract engineers, this is the moment the feature surface hardens.

Client Status Across Devnet 6 and Devnet 7

EIP-2780 and EIP-8037 sit at the center of execution-layer testing. ePBS behavior is being finalized. Prysm, Nimbus, and Lodestar have already passed relevant tests. Teku is updating its branch. Grandine is expected to become ready shortly.

Devnet 6 is still operational at approximately 80% participation. A Nethermind disagreement involving storage reads during reverts is under investigation. Earlier rounds surfaced issues across Besu, Prysm, Nimbus, Teku, and Erigon.

This matters. Storage-read semantics during revert directly affect how contracts observe state under failure paths. Any code that mutates transient state and reverts will surface cross-client inconsistencies first. Deployments that depend on a single client's revert behavior are exposed.

EIP-7928 and Block Access Lists Ship Now

The ACDC made a binding call. An additional change proposed for EIP-7928 will be included in Devnet 7 rather than deferred to a hypothetical Devnet 8. The updated Execution Layer test release incorporating this change was assigned as an immediate action item.

Block Access Lists expose which state locations a block touches during execution. The effect on clients is concrete. They can prefetch state data earlier. They can prepare parallel execution paths. They can reduce redundant reads. For contract authors, the implication is indirect but material. Gas pricing on state-heavy operations may shift once BAL-aware scheduling is live. Access pattern analysis becomes a first-class protocol feature rather than a profiler afterthought.

The Freeze and the Action Set

After Devnet 7 begins operating, structural EIP changes face a higher threshold. Gas-cost parameter adjustments for core Glamsterdam EIPs can still be considered if benchmark data justifies them. Larger modifications will not.

Verification items before public testnets:

• Audit revert-path state assumptions. Run the suite against multiple execution clients, not one.
• Stress-test storage access patterns. BALs will surface hot spots in production traces.
• Re-estimate gas against the latest spec. Do not anchor on Devnet 6 numbers.
• Pin client versions in CI. Teku's branch is still moving. Grandine is not yet shipped.

The feedback window on Glamsterdam's feature surface is closing. What lands in Devnet 7 is, for practical purposes, what ships in the hard fork.