Ethereum’s new ERC‑7730 Clear Signing customary replaces hex gibberish in pockets prompts with human‑readable, auditable transaction summaries to slash phishing and blind signing losses.
Abstract
- The Ethereum Basis’s Clear Signing working group and Ledger co‑designed ERC‑7730, a typical that turns right this moment’s cryptic pockets calldata into plain‑language transaction summaries.
- Clear Signing makes use of a JSON description format, a public registry tied to contract addresses, and third‑occasion audits so wallets can present correct, WYSIWYS intent with out altering on‑chain logic.
- The push comes as phishing and approval scams outpace protocol hacks; incidents just like the CoW DAO area hijack and Binance’s 22.9M blocked phishing makes an attempt present why legible prompts are vital.
The Ethereum Basis’s Clear Signing working group has printed a brand new open customary designed to exchange the cryptic, machine-readable hex information that wallets at present show when customers are requested to approve a transaction, in response to an official Ethereum Basis weblog put up. Constructed on the ERC-7730 specification, Clear Signing standardizes how transaction intent is described, displayed and verified throughout wallets, aiming to provide customers a plain-language abstract of what is going to truly occur on-chain earlier than they click on approve.
ERC-7730 and the top of unreadable transaction prompts
The issue Clear Signing addresses is certainly one of crypto’s oldest and most exploited UX failures. When a person interacts with a wise contract — whether or not approving a token spend, itemizing an NFT, or authorizing a DeFi place — most wallets right this moment show uncooked calldata or a partial ABI decode that’s unreadable to anybody who is just not a developer. That hole between what the display reveals and what the transaction truly does is the core mechanic behind a good portion of phishing assaults, the place malicious dApps current a benign-looking interface whereas the underlying transaction drains a pockets. Ledger, which co-developed ERC-7730 alongside the Ethereum Basis working group, has described the usual as a direct response to that assault floor, noting that “blind signing” has been one of many high two causes of great person losses in {hardware} pockets incidents.
Clear Signing’s structure has three parts. First, a unified JSON-based description format tied to ERC-7730 that dApp builders use to annotate their contracts with human-readable explanations of every operate name and parameter. Second, a public registry the place these descriptions are saved, versioned and linked to deployed contract addresses so wallets can pull the related metadata at signing time. Third, an impartial verification and auditing layer the place third events can assessment and attest to the accuracy of a contract’s descriptions, making a belief chain between the dApp developer’s intent and what the pockets in the end shows.
WYSIWYS: what modifications for customers and what stays the identical
The usual is explicitly designed to be non-breaking. Clear Signing doesn’t alter how transactions are structured, broadcast or settled on-chain, which means current sensible contracts, Layer 2 networks and DeFi protocols require no modifications to profit from it. The development is fully within the pockets presentation layer: as an alternative of exhibiting a uncooked hex string or a partial parameter dump, a Clear Signing-compatible pockets will show one thing like “Approve Uniswap to spend as much as 500 USDC out of your pockets” or “Listing CryptoPunk #4156 on the market at 40 ETH on OpenSea” — a exact, audited, human-readable description derived from the ERC-7730 registry entry for that contract.
For the broader Ethereum safety ecosystem, Clear Signing arrives at a second when wallet-level phishing and approval scams stay the dominant assault vector for retail customers at the same time as protocol-level exploits turn into tougher to execute on mature, audited contracts. A current crypto.information story on the CoW DAO area hijacking incident — the place attackers redirected customers to a phishing website for 4.5 hours and induced them to signal malicious transactions — illustrated exactly the failure mode Clear Signing is designed to mitigate: customers who may learn what they had been signing would have had a a lot better likelihood of catching the anomaly earlier than approving the drain. In parallel, a crypto.information story on Ethereum’s Glamsterdam devnet progress detailed how the Basis is concurrently advancing execution-layer upgrades and management restructuring, with Clear Signing becoming right into a broader push to make Ethereum safer and extra accessible at each layer of the stack with out ready for protocol-level modifications to propagate. As a crypto.information story on AI-enabled crypto fraud famous, Binance’s personal safety information reveals 22.9 million phishing makes an attempt intercepted in Q1 2026 alone — a quantity that underscores why making transaction approval legible to peculiar customers is now not a UX nicety however a safety crucial.