Ethereum's glamsterdam-devnet-7 carried heavier transaction loads through the Soldøgn developer sprint without falling over, but the same weekend exposed two block builders that were not consistently winning bids. Client teams patched across the weekend, and devnet-8 is tentatively penciled for early August, gated on final gas repricing numbers and mandatory EIP-8070 engine API changes.
Ethereum's glamsterdam-devnet-7 absorbed increased transaction loads over the Soldøgn weekend without falling over, according to All Core Devs Testing notes published July 27. Yet the same write-up flagged a rougher result: Geth Builder and Nethermine weren't consistently winning bids.
Glamsterdam is the cross-client devnet cycle where Ethereum's execution and consensus client teams, builders and protocol researchers run near-final code until it breaks or proves boring, ahead of public testnets and mainnet. Soldøgn sat inside that cycle as a concentrated developer sprint rather than a public testnet event.
Builder bids, not throughput, produced the finding that matters
Builders missing bids hints at competitiveness or integration gaps between builders, relays and proposers when blocks get dense — the scenario MEV-aware infrastructure must handle cleanly. Integration drift, timing paths that only matter under higher load, and diverging gas semantics can each skew a builder's view of a profitable bundle against the network's view.
Several clients rolled in fixes over the weekend to close gaps the load tests exposed, per the same notes. Because multiple major builders misbehaved under one stress profile, the sprint appears to have handed client teams and relay operators a shared, reproducible bug instead of scattered reports.
From "regular gas" to "execution gas"
On July 27, client teams referenced a live pull request renaming the EIP-8037 term "regular gas" to "execution gas". The goal is clarity: separate what pays for EVM execution from other categories so implementations and tooling use the same language.
Gas labels bleed into fee markets, wallet gas fee estimates and how builders pick transactions. Therefore, if two clients or libraries name the same accounting bucket differently, mispriced transactions or confusing RPC responses follow.
Devnet-8 targets early August
Teams tentatively penciled the move from DevNet-7 to DevNet-8 for early August, with a short list of must-haves: land the final repricing values and roll in mandatory EIP-8070 engine API changes. The final repricing numbers count as a gating item for the next devnet, so the calibration work — which operations should cost what, under load — has to settle first.
Earlier in the cycle, glamsterdam-devnet-6 went live on June 25, 2026 and ran with Gloas switched on from epoch 30, a detail collated by the EthPandaOps team. Their event matrix covering June 25 through July 9 shows how clients observed and emitted the same state over time.
Engine API changes ripple into every execution client, relay and builder path, so making EIP-8070 mandatory sets the line for DevNet-8: update, or don't participate.
Sources: All Core Devs Testing #89, EthPandaOps, Crypto Daily
Trading involves risk.
Risk Disclaimer
