Skip to content
Basis Desk

New from Basis Desk: free Telegram proxies for places where Telegram is blocked or slowed down.Connect in one tap →

Ethereum & L2s · 2 min read

Ethereum Foundation Explores Native Transaction Assertions Under EIP-7906

The proposed mechanism aims to stop blind signing and outcome mismatches by reverting transactions when post-execution state diffs breach signed rules.

Editorial oversight: Julian Mercer, Chief Editor
Neutral

At a glance Proposed

What happened
The Ethereum Foundation published research exploring native transaction assertions and EIP-7906 to enforce transaction outcomes onchain.
Why it matters
Native assertions would allow the EVM to revert transactions if net balance, storage, or logic changes violate pre-signed user conditions.
Who is affected
Ethereum wallet builders, smart contract developers, and users exposed to frontend hacks or slippage.
What's next
Core developers must decide whether to move EIP-7906 from 'Considered for Inclusion' to accepted status for the Hegotá upgrade.
Primary source
Ethereum Foundation Blog: How native transaction assertions could enforce a transaction's final outcome

Key points

  • The Ethereum Foundation proposed native transaction assertions to verify final state outcomes and eliminate intent and outcome mismatches.
  • EIP-7906 introduces three read-only opcodes—TXTRACE, TXDIFF, and EVENTDATACOPY—within an EIP-8141 POST_TX frame to revert failed checks.
  • EIP-8141 is slated for the Hegotá hard fork, while EIP-7906 is marked as "Considered for Inclusion" but not yet finalized.

The Ethereum Foundation is evaluating native transaction assertions to enforce the final outcomes of onchain transactions 1. Announced on Oct. 5, 2026, under the foundation's Trillion Dollar Security initiative, the research outlines mechanisms to let the Ethereum Virtual Machine (EVM) inspect net state diffs and revert calls that violate pre-signed rules 1.

At the time of writing, $ETH traded at $2,701, with total crypto market capitalization standing at $2.87 trillion. While existing defenses like simulation and Clear Signing clarify user requests, the foundation noted they fail to prevent outcome mismatches when frontends are compromised, proxy implementations shift, or onchain liquidity is exhausted 1. The paper cited past losses—such as the Bybit Safe implementation hijack, the BadgerDAO frontend exploit, and a swap where an Aave and CoW user received $36,000 worth of tokens for $50.4 million in collateral—to demonstrate that standard signatures govern execution requests rather than their ultimate results 1.

The EIP-7906 Proposal

To enforce post-execution conditions, developers are exploring EIP-7906, which introduces native transaction assertions using state difference opcodes 1. Built on top of frame transactions defined under EIP-8141, the proposal appends a read-only POST_TX frame at the end of execution to evaluate the net changes produced across balances, storage, contract deployments, and events 1.

Under this design, three prospective EVM instructions would facilitate the checks: TXTRACE to list state adjustments, TXDIFF to retrieve specific beginning and ending storage or balance values, and EVENTDATACOPY to read emitted event parameters 1. These opcodes operate exclusively inside the terminal static call frame 1. If an assertion check fails, the transaction's execution body reverts, but the transaction remains logged in the block with a failed status to ensure gas is paid and prevent denial-of-service spam on block builders 1.

While EIP-8141 is scheduled for inclusion in the upcoming Hegotá upgrade, EIP-7906 has reached the "Considered for Inclusion" stage and remains unconfirmed 1. For assertions to be effective, wallet software and protocol contracts must mandate them, requiring protected endpoints to actively reject calls that omit the necessary validation frames 1.

Questions this story raises

What is the difference between an intent mismatch and an outcome mismatch?
An intent mismatch occurs when a compromised interface tricks a user into signing a call they did not intend, while an outcome mismatch occurs when a correctly signed request encounters unfavorable liquidity, ordering, or contract states during execution.
What happens to gas fees if a native transaction assertion fails?
If an assertion rule fails inside the POST_TX frame, the state execution reverts, but the transaction is still registered onchain with a failed status and the gas payer is billed for the consumed compute to prevent denial-of-service attacks.

Sources

  1. [1] How native transaction assertions could enforce a transaction's final outcome — Ethereum Foundation Blog, October 5, 2026

Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

Community read
How do you read this story for the assets involved? One vote a day, anonymous.
Be the first to vote

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.