A draft Ethereum proposal, EIP-7906, would let on-chain code check what a transaction actually did and reverse it if the result breaks rules the user set in advance. The Ethereum Foundation framed the idea as a fix for blind signing, and it targets inclusion in the Hegotá upgrade expected in 2027.
The Ethereum Foundation highlighted a new proposal called native transaction assertions in a blog post on October 5, 2026, aimed at one of crypto's oldest weak spots: blind signing. A wallet shows a request with unclear or unreadable details, and the user approves anyway. The new mechanism would instead let code verify the outcome after the fact and undo it if something doesn't match.
What EIP-7906 adds to the EVM
That proposal, called EIP-7906, introduces three new opcodes to the EVM: TXTRACE, TXDIFF, and EVENTDATACOPY. These give on-chain smart contract code a way to inspect the real state changes a transaction produced, shifting verification from what a transaction claims it will do to what it demonstrably did.
The Ethereum Foundation tied the work to its Trillion Dollar Security initiative, which already includes Clear Signing, a measure focused on making transaction requests legible before a user approves them. Clear Signing works before execution; native transaction assertions work after it, checking whether the result matched expectations.
How the revert mechanism works
EIP-7906 depends on EIP-8141, the frame transaction format, which breaks a single transaction into distinct frames. EIP-7906 adds a new POST_TX frame that runs as a static call, a read-only check, after execution. If the conditions defined in that frame are not met, the transaction's effects can be reverted.
Where the proposal stands
EIP-7906 remains in draft status. The goal is to include it in the Hegotá upgrade, anticipated for deployment in 2027, and preliminary demonstrations have already run on a development network. Because EIP-7906 depends on EIP-8141, its fate is tied to whether the frame transaction format also makes the cut.
Developers will still need to work out how ordinary users define the rules their transactions must satisfy, since a safety net that requires expert configuration risks protecting mostly experts. Every new opcode also expands the surface area that must be implemented and audited across Ethereum clients, a trade-off any security gain has to justify.
Source: Crypto Briefing
Trading involves risk.
Risk Disclaimer
