Ethereum’s Clear Signing standard tackles blind transactions with ERC-7730

Ethereum’s new ERC‑7730 Clear Signing standard replaces hex gibberish in wallet prompts with human‑readable, auditable transaction summaries to slash phishing and blind signing losses.

The Ethereum Foundation’s Clear Signing working group has published a new open standard designed to replace the cryptic, machine-readable hex data that wallets currently display when users are asked to approve a transaction, according to an official Ethereum Foundation blog post. Built on the ERC-7730 specification, Clear Signing standardizes how transaction intent is described, displayed and verified across wallets, aiming to give users a plain-language summary of what will actually happen on-chain before they click approve.

ERC-7730 and the end of unreadable transaction prompts

The problem Clear Signing addresses is one of crypto’s oldest and most exploited UX failures. When a user interacts with a smart contract — whether approving a token spend, listing an NFT, or authorizing a DeFi position — most wallets today display raw calldata or a partial ABI decode that is unreadable to anyone who is not a developer. That gap between what the screen shows and what the transaction actually does is the core mechanic behind a significant portion of phishing attacks, where malicious dApps present a benign-looking interface while the underlying transaction drains a wallet. Ledger, which co-developed ERC-7730 alongside the Ethereum Foundation working group, has described the standard as a direct response to that attack surface, noting that “blind signing” has been one of the top two causes of significant user losses in hardware wallet incidents.

Clear Signing’s architecture has three components. First, a unified JSON-based description format tied to ERC-7730 that dApp developers use to annotate their contracts with human-readable explanations of each function call and parameter. Second, a public registry where those descriptions are stored, versioned and linked to deployed contract addresses so wallets can pull the relevant metadata at signing time. Third, an independent verification and auditing layer where third parties can review and attest to the accuracy of a contract’s descriptions, creating a trust chain between the dApp developer’s intent and what the wallet ultimately displays.

WYSIWYS: what changes for users and what stays the same

The standard is explicitly designed to be non-breaking. Clear Signing does not alter how transactions are structured, broadcast or settled on-chain, meaning existing smart contracts, Layer 2 networks and DeFi protocols require no changes to benefit from it. The improvement is entirely in the wallet presentation layer: instead of showing a raw hex string or a partial parameter dump, a Clear Signing-compatible wallet will display something like “Approve Uniswap to spend up to 500 USDC from your wallet” or “List CryptoPunk #4156 for sale at 40 ETH on OpenSea” — a precise, audited, human-readable description derived from the ERC-7730 registry entry for that contract.

For the broader Ethereum security ecosystem, Clear Signing arrives at a moment when wallet-level phishing and approval scams remain the dominant attack vector for retail users even as protocol-level exploits become harder to execute on mature, audited contracts. A recent crypto.news story on the CoW DAO domain hijacking incident — where attackers redirected users to a phishing site for 4.5 hours and induced them to sign malicious transactions — illustrated precisely the failure mode Clear Signing is designed to mitigate: users who could read what they were signing would have had a much better chance of catching the anomaly before approving the drain. In parallel, a crypto.news story on Ethereum’s Glamsterdam devnet progress detailed how the Foundation is simultaneously advancing execution-layer upgrades and leadership restructuring, with Clear Signing fitting into a broader push to make Ethereum safer and more accessible at every layer of the stack without waiting for protocol-level changes to propagate. As a crypto.news story on AI-enabled crypto fraud noted, Binance’s own security data shows 22.9 million phishing attempts intercepted in Q1 2026 alone — a volume that underscores why making transaction approval legible to ordinary users is no longer a UX nicety but a security imperative.