Ethereum Wallets Move to End Blind Signing With Clear Signing Initiative

A coalition of major wallets and security firms — Ledger, Trezor, MetaMask, Keycard, WalletConnect, Argot, and Fireblocks among them — is publicly backing an Ethereum-wide effort to standardize what's being called Clear Signing, according to reporting from Cointelegraph. The goal is straightforward: kill the practice of blind signing, the long-standing pattern where users approve a transaction without their wallet being able to show them, in plain language, what the transaction actually does.

What blind signing actually is

When you interact with a smart contract — swap a token on a DEX, mint an NFT, approve a spending allowance — your wallet builds a transaction whose payload is encoded calldata. For straightforward ETH transfers, the wallet can show you 'send 0.5 ETH to 0xabc...'. For contract interactions, what the wallet often shows is a long hex string and a contract address, neither of which means anything to a non-developer. So users learn to click 'Approve' and hope. Most of the well-known wallet drainer attacks in the last few years exploit exactly this gap: a transaction that visually looks routine but is actually granting an attacker spending rights or transferring an NFT.

How Clear Signing works

Clear Signing is a set of standards that lets contracts publish, in a machine-readable way, what each of their functions does and what the arguments mean. When you sign a transaction, the wallet pulls that metadata and shows a human-readable description: 'Approve Uniswap to spend up to 100 USDC' instead of a hex blob. The standard relies on contract authors publishing signed metadata and on wallets implementing the parsing logic. Neither piece works without the other, which is why the coordinated wallet-and-contract approach matters — it requires industry-wide buy-in, not a single vendor.

Why this is a real upgrade

Crypto security has historically been treated as a user education problem. The thinking goes: if users would just read the contract, verify the address, and pay attention, the drainers wouldn't work. That framing has always been a cop-out. Most users cannot read calldata, and asking them to is asking them to read assembly. Clear Signing reframes the problem as a tooling problem and solves it where it should be solved — at the wallet UX layer. It's the most credible attempt yet at making self-custody safer without making it harder.

What this means in practice

For someone who already self-custodies, this won't feel like a sudden change. Adoption will be rolling: dApps that publish Clear Signing metadata will start showing readable transactions in compatible wallets, while older or non-adopting contracts will keep showing the same hex blobs they always did. The progress will be visible in the wallet UI over the coming months. For tools that focus on contract risk and token approval hygiene — our own contract scanner included — the standard is complementary. Clear Signing helps you understand what a single transaction does; approval auditing helps you understand what your wallet has accumulated permission to do over time. Both layers matter.