web3wagmi
← All standards

EIP-7979 Call and Return Opcodes for the EVM

DraftCorecreated 2025-12-172 later proposals build on it

Three new instructions to support calls and returns.

Authors: Greg Colvin (@gcolvin), Martin Holst Swende (@holiman), Brooklyn Zelenka (@expede), John Max Skaller

Built on by (2)

Later proposals that name this one in their requires field.

EIP-8013Static relative jumps and calls for the EVMEIP-8337Validated EVM Code

What the specification covers

AbstractMotivationSpecificationCALLSUB (0x..)CALLDEST (0x..)RETURNSUB (0x..)CostsRationaleWhy no immediate arguments or code sections?Why may JUMP land on a CALLDEST?Why these three instructions?Why the return-stack mechanism for calls and returns?Safety advantages of the return stackAre there code size and gas savings?Are there real-time performance gains?Does ZK-rollup efficiency improve?Backwards CompatibilityTest CasesSimple routineTwo levels of subroutinesFailure 1: invalid destinationFailure 2: empty return stackSubroutine at end of codeReference ImplementationSecurity ConsiderationsCopyright

This proposal declares no Solidity interface, so there is nothing to compute. It may be a core protocol change, a meta proposal, or written in prose only.

Compare with

Parsed from the canonical specification · discussion