# Ethereum Draft Adds CALLSTATUS to Distinguish Reverts From Halts

Published 2026-10-26 · Crypto.world Team · Crypto.world

> An Ethereum draft proposes CALLSTATUS, a 2-gas EVM instruction that reports how a call or contract creation ended. The proposal aims to help contracts separate deliberate reverts from exceptional halts, while several design questions and implementation work remain open.

> “The EVM knows the outcome exactly at every frame boundary; this instruction exposes it.”
>
> [CALLSTATUS draft, submitted by svlachakis](https://github.com/ethereum/EIPs/pull/12586)

An Ethereum proposal would give smart contracts a direct readout of how their most recent call or contract-creation operation ended, rather than leaving them to infer the result from remaining gas. The draft calls the proposed EVM instruction CALLSTATUS and assigns it a tentative opcode, 0xA5, with a cost of 2 gas. It appeared in a draft pull request on October 25, 2026; a discussion thread followed on October 26.

## Five reported outcomes, one current frame

CALLSTATUS would report on the latest CALL, CALLCODE, DELEGATECALL, STATICCALL, CREATE or CREATE2 operation in the current execution frame. Its three bits represent whether the operation reverted, halted exceptionally, or encountered a halt farther down the call chain. The draft lists five possible values: 0 for success, 1 for a revert or an operation that did not start, 2 for an exceptional halt, 4 for success despite a halt below, and 5 for a revert after a halt below.

That distinction targets a problem for contracts that continue running after another contract call fails. A transaction sender can choose how much gas to forward, potentially making a call run out of gas; the calling contract may then mistake that failure for a deliberate revert. The proposal says contracts now rely on gasleft() arithmetic to make that distinction, a method that can break when gas costs change.

## Why the halt flag follows intermediaries

The draft carries a “sticky” halt flag upward through nested calls, including when an intermediate contract returns or reverts. That matters for common call paths such as proxies, wrappers that attach a revert reason, batches that continue after a failed call, and ERC-1271 signature checks. Without the flag, an intermediary could conceal an exceptional halt and leave its caller with what looks like an ordinary revert.

Under the proposal, a status of 2 or higher means gas forwarded somewhere along the call chain was consumed by an exceptional halt or an address collision. The draft frames that as a safer signal for contracts deciding whether a failure can be treated as final. It also acknowledges a trade-off: an earlier halt can mark a later, otherwise deliberate revert as status 5.

## Opcode and compiler questions remain open

The proposal is not an approved or implemented Ethereum change. Its pull request remains in Draft status, and the discussion thread says no external reviews had been completed as of October 26. The opcode itself is unsettled: the authors moved it from 0x4D to 0xA5 because another proposal uses 0x4D, but the draft still flags its final assignment as an open issue.

Other questions include whether to expose status 4, how a compiler such as Solidity might surface the halt bit through try/catch, and whether EIP-8141 frame transactions should expose matching codes through FRAMEPARAM. The discussion also calls for a prototype and execution-spec tests covering 58 listed cases. Those are outstanding tasks, not evidence that the instruction has been implemented.

## CALLSTATUS reports outcomes, not intent

The proposal would not identify why a contract halted. A callee could deliberately execute INVALID and produce an exceptional halt, and a revert that depends on gasleft() without an actual halt would remain subject to the sender’s control. The draft also says existing deployed contracts would not read the new status; only code written to use the instruction after adoption could act on it.

For now, CALLSTATUS is a proposed way to expose execution results that the EVM already knows at frame boundaries. Its practical value depends on resolving the opcode and interface questions, producing the promised tests and prototype, and moving the proposal beyond draft review.

## Sources

1. Original source [Ethereum Improvement Proposals on GitHub](https://github.com/ethereum/EIPs/pull/12586) github.com

Other pages read

2. [Fellowship of Ethereum Magicians](https://ethereum-magicians.org/t/eip-draft-callstatus-instruction/30085) ethereum-magicians.org

## Related stories

- [Ethereum Researcher Proposes Cheaper Replay-Protection Storage](https://crypto.world/news/ethereum-replay-protection-storage-costs)
- [Ethereum Draft Would Permanently Bar EIP-7702 Delegation](https://crypto.world/news/ethereum-draft-permanent-eip-7702-delegation-opt-out)
- [Ethereum Draft Sets Out Post-Quantum Keys for Validators](https://crypto.world/news/ethereum-draft-post-quantum-validator-key-registry)
- [Ethereum Draft Targets a Fourfold Cut in Finality Time](https://crypto.world/news/ethereum-eip-8453-decoupled-consensus-finality)
- [Ethereum Draft Reworks PeerDAS for Post-Quantum Security](https://crypto.world/news/ethereum-draft-post-quantum-peerdas-variable-size-blobs)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/ethereum-callstatus-instruction-draft
