What happened
On 18 October 2026, a change was merged into the Ethereum EIPs repository (merged by EIP‑Bot) that updates EIP‑8151 and references EIP‑8038. The edit clarifies the treatment of "empty failure output" and incorporates considerations for access gas accounting. The repository update is a specification-level change in the EIPs collection.
What the EIPs address, in plain language
-
Empty failure output (EIP‑8151): When a contract call fails, the EVM can return data that explains the failure. "Empty failure output" refers to cases where no such data is returned. The updated text clarifies how implementations and tools should treat situations where failure returns no data, removing ambiguity about expected execution semantics.
-
Access gas (EIP‑8038): This concept concerns how gas is charged for certain resource accesses during execution. The update aligns EIP‑8151’s wording with EIP‑8038’s approach to gas accounting so that the specification consistently describes when and how gas should be charged for accesses referenced by these EIPs.
Why this matters
The merged change is developer‑facing: it refines the specification that implementers, tooling authors, and smart contract developers rely on. Clearer rules about failure return data and gas accounting reduce ambiguity when writing contracts, building testing suites, and implementing EVM behavior in clients and development tools.
Who is affected
- Smart contract authors and auditors: clearer semantics can change how failure modes are interpreted in testing and formal analysis.
- Tooling and library authors: test suites, debuggers, and libraries that read or simulate failure return data may need to review expected behavior.
- Client and runtime implementers: specification clarifications are relevant when implementing EVM semantics and gas metering in execution environments.
What to do next
The merge is a change to the EIPs repository text; it does not by itself indicate network activation or client upgrades. Developers and implementers should review the updated EIP text in the repository to understand the precise wording and consider whether tests, tooling, or client behavior need adjustment.
Further reading
Consult the merged EIP text for exact wording and rationale in the repository commit linked below.