The Ethereum Foundation and a coalition of wallet developers launched a security standard on May 12 called “Clear Signing” that aims to translate the gibberish users see when approving transactions into something they can actually read.
The problem is straightforward: right now, signing a crypto transaction on most wallets means staring at a wall of hexadecimal characters and hoping you’re not authorizing a complete drain of your assets. The new standard, built on a proposed specification called ERC-7730, would replace that unreadable mess with plain descriptions of what’s moving, where it’s going, and what permissions you’re granting.
The Blind Signing Problem Behind Billions in Losses
Think about the last time you signed a transaction on an Ethereum wallet. Unless you’re a developer who reads raw bytecode for fun, the approval screen probably looked like alphabet soup. A long string starting with “0x” followed by dozens of characters that could mean “send 0.5 ETH to your friend” or “grant infinite spending permission to a contract that will empty your wallet in three seconds.”
This is what the industry calls blind signing. You’re effectively signing a contract written in a language you don’t speak, trusting that whoever built the interface is showing you the real intent behind the code.
Attackers have exploited this gap relentlessly. The Ethereum Foundation specifically cited the Bybit hack as an example of how blind signing creates openings for sophisticated phishing operations. The pattern is consistent across incidents: users visit a compromised or spoofed website, connect their wallet, and approve what looks like a routine transaction. The approval actually grants unlimited access to their tokens, which the attacker drains seconds later.
The losses have accumulated into the billions. And the frustrating part is that victims often did nothing obviously wrong. They didn’t share their seed phrase or fall for a Nigerian prince email. They just couldn’t read what they were signing.
How ERC-7730 Translates Code into Plain English
The Clear Signing framework addresses this through a surprisingly elegant structure. At its core sits a public registry where transaction descriptions can be submitted and independently verified by security researchers.
Here’s the mechanics: when a decentralized application sends a transaction to your wallet, that transaction contains specific function calls and parameters encoded in the Ethereum Virtual Machine’s format. Under the current system, your wallet just displays this raw encoding. Under ERC-7730, wallet developers can query the public registry to find a human-readable description of what that specific function call actually does.
So instead of seeing:
0xa9059cbb000000000000000000000000d8da6bf26964af9d7eed9e03e53415d37aa96045
You might see:
- Action: Transfer tokens
- Asset: 500 USDC
- Recipient: 0xd8da…6045 (vitalik.eth)
- Permissions: One-time transfer only
The registry operates on a trust model where wallets choose which sources they consider reliable for transaction descriptions. This means different wallets could potentially show different descriptions for the same transaction, depending on which verifiers they trust. The Ethereum Foundation’s Trillion Dollar Security Initiative will oversee the core infrastructure, but the framework is designed to be decentralized rather than dependent on any single authority.
One engineering consideration worth noting: the registry can only provide descriptions for known contracts and function calls. A brand-new malicious contract with custom functions won’t have registry entries, so wallets would still need to flag unsigned or unverified transactions differently than those with established descriptions. The standard addresses the 80% case of phishing through known attack patterns, not the edge case of novel zero-day exploits.
Industry Response and the Trezor Endorsement
The reaction from major hardware wallet manufacturer Trezor was unequivocal. Chief Technology Officer Tomáš Sušánka called Clear Signing “a critical security advancement for our entire industry” in a statement to CoinDesk.
“When users can’t understand what they’re signing, security becomes much more difficult. This standard changes that, and every wallet provider should embrace it,” Sušánka said.
The endorsement matters because hardware wallets like Trezor and its competitors serve as the last line of defense for users who prioritize security. These devices require physical confirmation of transactions, which theoretically gives users a chance to review what they’re approving. But that review is meaningless if the approval screen shows unreadable code. Clear Signing would make hardware wallet confirmations actually functional for non-technical users.
The timing also reflects where Ethereum sits in its adoption curve. The network has moved well beyond early-adopter enthusiasts. Institutional players, mainstream retail users, and increasingly regulated financial products all touch Ethereum infrastructure. These users aren’t going to learn to read bytecode, and the network can’t continue losing them to preventable phishing attacks without undermining its mainstream aspirations.
The Ethereum Foundation has been active on multiple fronts this year. In an unrelated move, the Foundation recently sold $22.9 million in ETH to BitMine as part of its treasury management operations, its second OTC deal with Tom Lee’s operation in 2026. The organization appears to be simultaneously managing its operational runway while investing in ecosystem infrastructure like Clear Signing.
What This Means for Everyday Crypto Users
Let’s run through a practical scenario. You’re on a DeFi protocol trying to swap tokens. The site asks you to approve a transaction. Under the current system, you see hexadecimal data, shrug, and click approve because you trust the domain you’re on.
Under Clear Signing with proper wallet support, you’d see something like:
- Protocol: Uniswap v3
- Action: Approve spending of 1,000 USDC
- Spender: Uniswap Router Contract (verified)
- Limit: 1,000 USDC (exact amount)
Now imagine you’re on a phishing site that looks identical to Uniswap. The transaction it sends might show:
- Action: Approve spending of USDC
- Spender: Unknown contract (not in registry)
- Limit: Unlimited
The difference becomes immediately obvious even to someone who has never looked at a smart contract. An unlimited approval to an unknown contract is a red flag anyone can recognize. The same transaction under the current blind signing model would look like the same wall of hex characters as the legitimate swap.
There’s a user education component that still matters here. Clear Signing doesn’t help users who click approve without reading anything at all. If you’re the type to dismiss every popup without a glance, a human-readable warning won’t save you. But it removes the excuse that users couldn’t have known what they were signing. The information gap closes.
For anyone actively using DeFi or NFT platforms, this standard could meaningfully change the risk profile of daily operations. Those who’ve lost funds to approval-based attacks often describe the frustrating realization that they technically authorized everything themselves. Clear Signing shifts the burden back toward attackers, who can no longer rely on user confusion as their primary exploit vector.
The broader security landscape in crypto continues evolving. We’ve seen projects like the MARA Foundation take different approaches to securing Bitcoin infrastructure through open-source funding and research grants. Clear Signing represents Ethereum’s answer to a different but equally important security layer: the human interface.
Wallet developers now face the question of implementation timelines. The standard exists. The registry infrastructure is being built. But users won’t benefit until their specific wallet of choice actually integrates ERC-7730 support and starts pulling descriptions from trusted registry sources. MetaMask, Coinbase Wallet, Rainbow, and other major players haven’t publicly committed to adoption timelines as of this writing.
The Security Calculation Going Forward
The Ethereum Foundation’s framing is notable. They’re not positioning Clear Signing as a silver bullet. The announcement explicitly acknowledges that better security “may depend less on smarter code and more on making sure users actually understand what they’re signing.”
This is a mature observation. The crypto industry has poured enormous resources into smart contract audits, formal verification, bug bounties, and protocol-level security. All of that matters. But an audited, verified, bulletproof smart contract can still be used maliciously if someone tricks a user into approving a drain. The weakest link has consistently been the human clicking the button.
Clear Signing represents an attempt to strengthen that link without requiring users to become technical experts. It’s the difference between posting a warning sign in a language nobody reads versus translating it into the local tongue.
The counterargument some will raise: sophisticated attackers will adapt. If registry-verified transactions become the norm, phishing operations will find ways to game the registry system or develop attacks that bypass it entirely. That’s probably true. Security is an arms race, not a solved problem.
But the current equilibrium is clearly broken. Billions in losses. Victims who did nothing unreasonable. A user experience that asks people to trust opaque code with their financial lives. Clear Signing doesn’t end the war, but it forces attackers to fight on harder terrain.
The standard launches with the backing of the Foundation and at least one major hardware wallet manufacturer. Whether it becomes the industry default depends on how quickly other wallet providers follow. Users who want to benefit should watch for ERC-7730 support announcements from their wallet of choice and consider switching to compliant options as they become available.
Signing a transaction should never feel like clicking accept on terms you can’t read. That’s what’s changing.
