The Ethereum Foundation rolled out a new 'Clear Signing' standard today, designed to stop users from blindly approving malicious transactions. The move comes after billions of dollars in losses from phishing attacks and wallet drains that exploit the way most crypto wallets present transaction data. The standard forces wallets and dapps to show approval requests in plain language, making it harder for attackers to hide dangerous actions inside unreadable hex code.
What Clear Signing changes
Right now, when a user approves a token transfer or signs a smart contract interaction, they often see a wall of hexadecimal strings. Most people just click 'confirm' without reading it — that's exactly what phishing attacks rely on. Clear Signing requires wallets to understanding that data into human-readable fields: which token, how many, which contract, what permissions. It standardizes the format so users can quickly tell if the request is legitimate or if it's trying to drain their wallet.
The Foundation says the standard is open-source and ready for integration. It doesn't change how Ethereum works under the hood — it just changes what the user sees before they sign.
Phishing attacks have been one of the most persistent threats in crypto. Fake airdrops, malicious approvals, and 'ice fishing' schemes have collectively drained billions from individual wallets and DeFi protocols. The problem isn't new, but the scale keeps growing. Clear Signing targets the root cause: the information asymmetry between what the user thinks they're approving and what the transaction actually does.
The timing isn't random. The Ethereum Foundation has been under pressure to improve user safety as more retail money flows into L2s and app chains. This standard is one of the first concrete outputs from its ongoing UX safety working group.
Adoption hurdles
A standard is only useful if wallets actually implement it. Major wallet providers like MetaMask, Rabby, and Safe will need to add support for the new format. Dapps will need to update their transaction request payloads to comply. The Foundation is pitching Clear Signing as a minimal-effort upgrade — most of the work is on the wallet side, not the smart contract side.
It's not mandatory. There's no enforcement mechanism. But the Foundation is betting that user demand will push wallets to adopt it, especially after high-profile hacks that could have been prevented with clearer signing prompts.
The standard is available now on the Ethereum Foundation's GitHub page. Developers can start integrating it today. Whether it becomes the default before the next big phishing wave is an open question.
