Draft EIP 8079 Proposes Native Rollups Through EXECUTE

What changed

Ethereum contributors published draft EIP 8079 on 13 November 2025 under the title Native rollups. The proposal would expose Ethereum’s state transition function to the execution layer through a new EXECUTE precompile. Rollups could reuse L1 logic more directly if the idea ships.

Authors include Luca Donno from L2Beat and Justin Drake from the Ethereum Foundation. The EIP remains in Draft status on the public EIPs repository. Draft status means no mainnet fork date exists yet.

Why it matters

Rollup teams today reimplement or verify L1 rules off chain. That work duplicates effort and adds audit risk. A native path could shrink audit surface and align fault proofs with exactly what L1 runs. That matters for teams planning multi year security reviews.

For protocol investors and wallet platforms, draft core EIPs are early signals. They show where client engineering hours may go next. Market hype often runs ahead of client code, so treat Draft text as a research spike, not as a ship date.

App devs feel impact only after clients ship testnets. Infra teams still start design reviews when Draft EIPs land. Wallet gas estimates may shift if EXECUTE style precompiles change calldata patterns.

Who is affected

Layer 2 engineering leads feel this first. So do rollup security auditors and node client maintainers. Exchanges and custody teams should track whether wallet software assumptions change if EXECUTE style precompiles alter gas and calldata patterns.

Application developers feel impact only after clients ship testnets. Infra teams start design reviews when Draft EIPs land. Bridge operators should note whether proof systems must replay L1 logic through the new precompile path.

Legal and compliance teams may ask whether draft protocol changes affect disclosures to users. Until Review status, most firms will log the EIP and wait for test vectors.

What to do next

Read the Draft EIP and the Ethereum Magicians thread linked from the header. Map which of your rollups depend on custom state transition code today. Note where a precompile could replace duplicated logic.

Do not treat Draft status as a deployment deadline. Use it to update long range research spikes for 2026 client roadmaps. Share a one page internal brief so exec sponsors know this is early stage.

Run no production changes based on Draft text alone. Spin up a reading group with security and client devs instead. List open protocol questions in your internal wiki.

What to watch

Watch client implementer feedback on the Magicians forum and whether the EIP moves from Draft to Review. Watch L2Beat and Foundation posts for test vectors or reference implementations.

Track competing rollup efficiency proposals so you can compare native STF access with other compression or proof system changes. Also watch gas benchmark posts once devnets exist.

Token price chatter will spike on social feeds. This desk brief tracks protocol design, not trading calls. Base product plans on client milestones, not on hourly market moves.

Node operators should subscribe to client release mailing lists for geth, nethermind, and besu. Draft EIPs often gain testnet code months before users notice in wallets.

Smart contract auditors should flag custom STF copies in rollup repos they review this winter. Duplicated logic is a prime place to swap in shared L1 calls if EIP 8079 matures.

Rollup product managers can add a slide to Q1 roadmaps that says native STF is a watch item. That sets exec expectations without promising ship dates.

Foundation grant teams may fund client work tied to this EIP if forum feedback stays active. Track grant posts so your lab knows when test code is ready to clone.

Wallet UX writers should draft user facing notes only after testnet demos exist. Early drafts confuse support when specs still change week to week.

Indexers that replay blocks should note whether EXECUTE calls change trace formats. Data teams need lead time before dashboards break on devnets.

Image: GitHub

Photo: Shubham Dhage / Pexels

Sources

• Primary — GitHub, EIP 8079 Native rollups (13 November 2025). Defines the EXECUTE precompile concept and Draft status.
• Secondary — Ethereum Magicians, EIP 8079 discussion thread (2025). Community review venue linked from the EIP header.