Ethereum developers are weighing a change that would add native transaction assertions to the protocol, a move aimed squarely at blind signing. The proposal would let the network verify what a transaction actually does before it goes through, rather than trusting whatever a wallet screen happens to display. If adopted, it would shift a security check that currently lives almost entirely in the wallet layer down into Ethereum itself.
What blind signing actually means
Blind signing is the gap between what a user thinks they're approving and what the contract will execute. A wallet shows a summary, a signature gets attached, and the underlying call runs — often against code the signer never reads. Attackers have learned to exploit exactly that gap, dressing up malicious approvals as routine ones. The proposal would insert assertions at the transaction level, so the check happens as part of the transaction rather than as a display step a wallet can get wrong or skip.
Why the wallet layer isn't enough
Wallets vary wildly in how much they understanding and how clearly they present it. Some simulate transactions, some show raw calldata, and plenty do neither well. That inconsistency is the problem the proposal is trying to route around. Putting assertions in the protocol means the verification doesn't depend on which interface a user happens to open. It also gives developers a standard to build against instead of each wallet inventing its own preview logic.
The institutional angle
Institutions have been slower to touch on-chain transactions for a fairly boring reason: risk controls are hard to audit when the last line of defense is a UI. A protocol-level assertion is easier to point at during a compliance review. It's a check that exists in the same place for everyone, not a feature that varies by vendor. That may be the proposal's most practical selling point — not a dramatic security upgrade, but a more legible one.
Still a proposal
Nothing is live yet. The idea is on the table, and proposals at this stage tend to get picked apart before anything ships — feasibility, gas costs, how assertions interact with existing contracts, and whether wallets would actually adopt the standard. The blind signing problem is real and well documented. Whether this is the fix Ethereum settles on is a separate question, and one the developer discussion will have to answer first.
