Ethereum Glamsterdam Upgrade Moves Toward Mainnet After Final Devnet Success

The upgrade ships two structural changes — enshrined proposer-builder separation (ePBS) and block-level access lists — both aimed at throughput and fee compression rather than a reversal of base-chain revenue trends.

Protocol mechanics

ePBS moves block construction rules into the protocol itself, removing the out-of-protocol MEV relay layer that has defined validator economics since the Merge. Block-level access lists let validators execute unrelated transactions in parallel, targeting a 200 million gas limit floor and lowering effective fees for transactions that opt into the mechanism.

• ePBS: on-chain block building, no external relay dependency
• Block-level access lists: parallel execution, 200M gas floor
• Net effect: compression of L1 fee variance, not a fee collapse

Actual fees still track demand. Capacity expansion ≠ lower fees if demand absorbs the headroom. ETH holders should not price in a structural fee rebound on this fork alone.

Timeline vs. reality

Past Ethereum forks needed two to four months of public testnet seasoning between final devnet and mainnet. Some trackers cite an end-of-August target; the wider realistic window is September through December. No block height or locked date has been announced by core developers as of the latest reporting.

Validator operators should track Holesky and Hoodi testnet releases as devnets transition. Retail holders do not need to act — staking positions and RPC endpoints remain unaffected at the application layer. The only concrete near-term deliverable is the public testnet calendar, not a fork activation.

Revenue context and verdict

Ethereum turned 11 this week hosting roughly $148.8 billion in stablecoins and around $15.5 billion in tokenized real-world assets, per TradingView and CryptoSlate data. Daily mainnet revenue dropped to approximately $330,000, with base-chain fees at $734,000 over a 24-hour period. The contradiction is structural: Ethereum remains the dominant settlement layer for dollar-denominated activity, but base-chain revenue compresses as execution migrates to rollups and alternative L1s. Glamsterdam inches capacity higher while the economic center of gravity continues to shift outward — a deliberate trade-off, not a bug.

For teams building exposure to that settlement infrastructure, the fork's timing matters less than compounding infrastructure decisions. Choices around subdomain or subdirectory for Web3 SEO shape how that traffic and liquidity actually find you over the next cycle.

Verdict: Glamsterdam is a throughput play with a soft delivery date. Watch Holesky and Hoodi progression for the first concrete signal on mainnet timing. Treat any "end of August" target as optimistic until core devs publish a block height.