Skip to content

EIP-8024: DUPN, SWAPN, EXCHANGE opcodes - #2874

Open
anvacaru wants to merge 2 commits into
amsterdam-foundationfrom
eip-8024
Open

EIP-8024: DUPN, SWAPN, EXCHANGE opcodes#2874
anvacaru wants to merge 2 commits into
amsterdam-foundationfrom
eip-8024

Conversation

@anvacaru

Copy link
Copy Markdown
Contributor

Implements EIP-8024: immediate-operand stack manipulation opcodes for legacy EVM.

  • evm.md: DUPN/SWAPN/EXCHANGE with one-byte immediates; schedule.md: Ghaseip8024 + gas.

Added helpers based on the EIP's reference functions:

  • #immByte(PGM, PC) reads the operand like PUSH does (#range, total, zero-padding at end-of-code),
  • #decodeSingle is the EIP's decode_single ((x+145) mod 256, mapping the valid bytes onto the contiguous depth range 17..235),
  • #decodePairA/#decodePairB are the two components of decode_pair (the pair is exposed as two projections; each dispatches to an arity-2 overload on the nibbles of x^0x8F, with complementary Q <Int R / Q >=Int R requires clauses).
  • #validSingle/#validPair implement the EIP's valid-immediate byte ranges; invalid immediates halt with EVMC_INVALID_INSTRUCTION, insufficient depth with EVMC_STACK_UNDERFLOW.

Jumpdest analysis is intentionally unchanged: valid immediates can never be a JUMPDEST or PUSH byte, which is the EIP's backward-compatibility property.

anvacaru and others added 2 commits July 24, 2026 22:08
Add the three backward-compatible stack opcodes (EIP-8024): DUPN (0xe6),
SWAPN (0xe7), EXCHANGE (0xe8), each with a 1-byte immediate and Gverylow (3)
cost, gated on the new Ghaseip8024 flag (true at AMSTERDAM). Modeled as
StackOps that read and decode their immediate from <program> at exec time
(like PUSH): decode_single ((x+145)%256, valid x in [0,90]u[128,255]) for
DUPN/SWAPN, decode_pair (k=x^143; divmod(k,16)) for EXCHANGE. DUPN(n)/SWAPN(n)
reuse the DUP/SWAP stack logic; EXCHANGE swaps two arbitrary positions.
Out-of-range immediates halt EVMC_INVALID_INSTRUCTION, insufficient depth
halts EVMC_STACK_UNDERFLOW; #widthOp is 2 (pc advances past the immediate).

Jumpdest analysis (#widthOpCode) is intentionally left unchanged: EIP-8024's
immediates are constrained to never be a JUMPDEST or PUSH byte, so scanning
the immediate as an ordinary opcode keeps old jumpdest analysis valid (the
backward-compatibility property; confirmed by the jump_to_immediate_byte
fixtures). Unmask all 53 eip8024 fixtures.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant