EIP-7906 could let Ethereum revert transactions if rules fail

Ethereum Foundation researchers are examining native transaction assertions that would require transaction safety to depend on the final state as well as the signed instructions, according to a research update published on October 5, 2026. The initiative aims to address specific risks in how users approve actions on the network.

The foundation identifies blind signing and uncertain execution outcomes as distinct mechanisms through which users can approve actions that result in unwanted consequences. Current transaction signatures prove authorization for specific bytes but do not guarantee that a complex smart-contract interaction achieves the signer’s intended economic objective. The proposed research explores independent checks that inspect net balance, storage, or code changes after execution. If a required rule fails during this post-execution inspection, the mechanism would revert the transaction.

EIP-7906 Implementation Path

EIP-7906 is identified as a possible route for implementing these assertions. The proposal utilizes a read-only post-transaction frame to evaluate changes and events before accepting the outcome. The foundation states that EIP-7906 is currently under consideration but is not yet confirmed for a future upgrade. Even if adopted, the implementation would require wallets or protocols to actively enforce the specific rules defined by the assertion.

Engineers working on this development must consider several design choices, including who defines the rule, the associated gas costs, and whether third-party software can silently omit the check. The technical work involves evaluating existing applications, node operators, and client compatibility. Additionally, developers must determine how errors behave under stressed network conditions. A change that appears straightforward at the protocol level can create significant coordination challenges across the ecosystem.

Research Limitations and Next Steps

The work remains at the research and proposal level and does not constitute a new safety guarantee available for ordinary Ethereum transactions today. The foundation notes that assertions sourced from a compromised interface could still encode a harmful outcome, meaning the mechanism does not eliminate all security risks. Performance claims associated with such changes require careful definitions of throughput, finality, responsiveness, cost, and fault tolerance, as improving one metric does not automatically improve others.

The development sits within a broader shift toward wallet security, where different stakeholders measure success differently. Users prioritize clarity and predictable access, operators focus on reliable controls and manageable costs, and institutions seek accountability in the event of failure. Future updates in this area should distinguish between released features, planned features, and measured use. Key areas to watch include EIP governance, wallet implementations, protocol support, and testing of the proposed state-difference opcodes.