Reporting window: October 19, 2026, 00:00:00 to October 26, 2026, 00:00:00 WITA (Asia/Makassar), end exclusive.

Ethereum’s immediate priority shifted from preparing Hoodi’s upgrade to understanding contract compatibility. At AllCoreDevs Execution on October 22, Ansgar Dietrichs canceled the scheduled Hoodi fork without a replacement date. He also held mainnet planning pending a fuller impact assessment; mainnet had never received an activation date. ChainSecurity’s analysis of gas refills and repricing supplied the technical reason to stop. The practical implication is that application recovery paths now deserve the same attention as client readiness. Meanwhile, Hegotá’s execution work retained a separate devnet target, and execution testing closed a receipt-verification gap.

Contract failure paths force a scheduling reversal

ChainSecurity examines EIP-8037: State Creation Gas Cost Increase and EIP-8038: State-Access Gas Cost Update. Its writeup predates this reporting window; the news is the resulting scheduling decision. The researchers show how restored gas can let a failure handler finish where it previously reverted. A contract may consequently commit a failed operation instead of leaving the operation retryable. ChainSecurity also warns that repricing can invalidate a fixed gas budget.

The concern does not establish that every gas check fails. ChainSecurity says a correctly bounded pre-call check can still guarantee gas delivery, provided the budget covers the new schedule. The next useful evidence is an assessment of affected call paths and mitigations, followed by a decision on whether the specification itself needs revision.

Daniel Lehrner and Potuz argued for preserving Hoodi before committing another testnet to potentially changing specifications. Barnabas Busa then merged the removal of Hoodi’s activation configuration on October 22. Lodestar’s merged follow-up restores an infinite fork epoch and removes the planned gas-limit increase. Those changes demonstrate implementation follow-through. They do not establish that every operator has installed a compatible release.

Hegotá keeps an execution devnet while frame fees change

Dietrichs set the following week as the target for Bogota devnet 2, with a combined execution-and-consensus devnet intended after Devcon. Nethermind, Geth and ethrex supported proceeding with the broader scope; Besu acknowledged that the timetable exceeded its readiness. These were commitments and a launch target, not a report of successful interoperability. Watch the actual launch and subsequent cross-layer testing.

The concrete specification change came from lightclient, who merged a single max_fee budget into EIP-8141: Frame Transaction on October 22. The specification caps aggregate cost across execution, state and blob gas. Spare budget for one resource can cover a price increase in another. The proposal retains resource-specific pricing and accounting. For wallets and paymasters, the review question is how the aggregate cap behaves across changing base fees. The merge changes the proposal text; it does not establish deployed client behavior.

Receipt checks make live-network test results more meaningful

LouisTsai-Csie’s merged execution-specs change closes a gap in TransactionPost.execute(). Previously, that path ignored expected_receipt: a test asserting only receipt status, gas or logs could pass without checking the assertion. The updated path fetches declared receipts and applies the same verifier used during fixture filling.

The author explicitly leaves block-access-list and block-header assertions unresolved, because live-network execution does not control block composition. The useful next signal is a rerun of receipt-dependent tests against named clients. A stronger test harness improves the evidence available for fork decisions; the merge alone supplies no new client pass rate.

Sources and further reading