Analysis · News

Ethereum EIP commits tighten EVM control-flow definitions

Ethereum EIPs 8173, 7979, 8337, and 8151 were updated, with EIP-7979 introducing a separate return stack and new control-flow instructions for the EVM.

Ethereum EIP commits tighten EVM control-flow definitions

Four Ethereum proposals were updated on August 28 — EIP-8173, EIP-7979, EIP-8337 and EIP-8151 — revising terminology, definitions and technical specifications. The primary GitHub commit shows the most concrete change sitting inside EIP-7979: explicit control-flow instructions meant to cut the complexity of calls and returns within the EVM.

EIP-7979 introduces three new control-flow instructions to the EVM: CALLSUB, RETURNSUB and JUMPSUB, as specified in the GitHub EIP-7979 commit.

The structural centerpiece is a second stack. EIP-7979 adds a “return stack” to the EVM machine state, dedicated to storing return addresses and kept entirely separate from the existing data stack. That data stack holds 256-bit words and tops out at 1,024 entries, as stated by EIP-7979 in the GitHub commit.

The proposal’s rationale is explicitly tied to EIP-8173, “Foundations of EVM Control Flow,” which defines the problem EIP-7979 is trying to solve. Anything worse than linear complexity in static analysis, the commit says, can become a denial-of-service vector for online static analysis, bytecode validation, and ahead-of-time and just-in-time compilation.

In the desk’s assessment, the revisions matter beyond wording because the affected surface for developers includes any tool that analyzes, validates or compiles EVM bytecode, and the proposed instruction model hands protocol implementers a more explicit specification to work from. The available material does not establish gas costs, detailed opcode semantics, compatibility with existing contracts, or a mainnet deployment timetable.

EIP-7979 was first created on December 17, 2025, as recorded in the GitHub EIP-7979 commit. The same day’s commits to EIP-8173, EIP-8337 and EIP-8151 introduced terminology and definition updates across the four proposals. What specifically changed in those three EIPs isn’t detailed in the available commit record.

The EIP-7979 material notes that EVM Object Format takes a complementary alternative design path — function descriptors in code sections, relative jumps via immediate arguments. EIP-7979 specifies a complementary alternative: explicit call and return instructions paired with a dedicated return-address stack. Developers comparing control-flow designs will find the distinction documented, though the available material doesn’t establish which approach moves forward.

As unrelated market context: CoinGecko lists EETH$2,434.792.74% at $2,431.75, down 2.8% over 24 hours. The EIP documents provide no implementation date, gas schedule or contract-compatibility result that would connect that price move to the commit activity.

eip-7979 eip-8173 ethereum evm github
Nadia Rahman

Nadia Rahman

Markets Editor · 9 years covering crypto · Author page

Nadia Rahman is CoinScoop's Markets Editor. She covers Bitcoin, macro liquidity and the spot-ETF complex, and previously reported on rates and FX for a global newswire.

Disclosure: This article is independent journalism and is for information only — it is not financial advice. CoinScoop is reader-supported and may earn a commission from some links. Read our disclosure policy →