Ethereum Clear Signing Is Live, but Coverage Is Partial

Ethereum’s Clear Signing initiative has moved beyond its May 2026 announcement: several wallets now display transaction details using the system, and hundreds of descriptors have been published. The important qualification is that ERC-7730 remains a draft and support is not universal, so blind signing has not disappeared.

That makes Clear Signing a functioning security layer rather than a completed ecosystem-wide switch. Users can benefit when their wallet, the relevant application and trusted metadata all support it; otherwise, a transaction may still arrive as raw or inadequately explained data.

What Ethereum launched in May 2026

On May 12, 2026, a working group of wallet developers, security companies and the Ethereum Foundation’s Trillion Dollar Security Initiative launched an open standard intended to reduce blind signing. The Ethereum Foundation announcement said the practice had contributed to billions in user losses, including the Bybit hack, and identified the foundation’s initiative as a steward of the registry infrastructure.

Blind signing occurs when the information shown by a wallet is insufficient for a person to understand the authorization being granted. A polished application can describe an action as a swap, claim or routine approval, while the wallet may expose only machine-oriented data. If the application interface has been compromised, trusting that interface alone defeats the value of reviewing the transaction on a separate signing device.

Clear Signing addresses that gap by giving wallets structured descriptions of a contract call or signed message. Instead of treating an opaque payload as the only reviewable information, a compatible wallet can identify the intended operation and format relevant fields such as an asset amount, destination or spending authority in a form a person can inspect.

ERC-7730 defines the format, not a mandatory wallet feature

The technical foundation is ERC-7730, a JSON descriptor format that supplements contract ABIs and structured-message schemas with display instructions and contextual intent. The current ERC-7730 specification is still marked Draft; it covers EVM contract calldata and EIP-712 messages and requires wallets to verify that a descriptor’s binding context matches the data being signed.

A descriptor can identify the relevant contract deployment, the function being called and the fields that should appear on the signing screen. It may also specify how values should be rendered—for example, as a token amount rather than an unscaled integer—and provide a short statement of intent. The wallet decodes the transaction, checks the descriptor’s constraints and builds the review display from the actual values being authorized.

This architecture supports existing contracts because the explanatory metadata is supplied alongside the transaction rather than embedded in every deployed contract. It also creates a dependency: the descriptor must be available, applicable to the correct contract and treated as trustworthy by the wallet. Publishing a format does not automatically update every wallet or produce accurate metadata for every application.

Adoption is real, but coverage remains partial

The latest published ecosystem snapshot, dated June 30, 2026, counted 380 descriptors covering 51 protocols. The Clear Signing ecosystem directory listed Ledger, Ambire and Gemini wallet implementations as live, while labeling Trezor support as in development.

Those figures are meaningful because they show that the project has progressed beyond a paper proposal. Descriptors have been published for applications in trading, lending, staking, payments, bridges, governance and other categories, and compatible wallets can already use metadata at signing time.

They also define the limit of the claim. Ethereum contains far more contracts and signing paths than the registry currently describes, and even a listed protocol may introduce new deployments, proxy implementations or functions that require updated metadata. A user’s actual protection therefore depends on the precise wallet, contract address, chain, message type and descriptor version involved in that transaction.

Why descriptors need their own security controls

Human-readable text is safer only when it faithfully represents the bytes being signed. A malicious or incorrectly applied descriptor could assign a familiar token name to the wrong contract, present a dangerous address as trusted or hide the meaning of a parameter. Clear Signing shifts part of the review problem from raw transaction data to the provenance, validation and precise application of metadata.

ERC-7730 addresses this with binding rules. A wallet must check that the transaction or message matches the descriptor’s declared context before applying its formatting. The specification also calls for warnings when external information cannot be verified and says untrusted information must not be presented as though it were verified.

The registry sits outside the core format, so governance remains important. The launch model combines open submissions with independent review and attestations, while each wallet decides which metadata sources it trusts. That preserves choice, but it also means two wallets may not provide identical coverage or accept the same registry entries.

What a readable approval can—and cannot—prove

A clear display can reveal a mismatch between what an application claims and what the transaction actually requests. An unexpectedly large allowance, an unfamiliar recipient or a different operation becomes easier to catch when the wallet renders the decoded fields accurately.

It does not prove that an investment, token or recipient is legitimate. Nor does it guarantee that a complex sequence will have the outcome the user expects after execution. Clear Signing improves the final authorization checkpoint; it does not replace contract audits, transaction simulation, phishing defenses or careful verification of addresses and amounts.

The practical rule is to treat readable details as evidence to inspect, not as a safety badge. If a wallet falls back to raw data, reports an unknown descriptor or cannot verify the relevant context, the protective layer is absent for that approval. The safest response is to stop unless the transaction can be independently understood.

The end of blind signing is a goal, not the current status

Ethereum now has a shared format, registry infrastructure, published descriptors and live wallet integrations. That is a substantial change from merely asking users to decipher hexadecimal data, and it gives application teams a concrete way to describe their calls across compatible wallets.

But the launch did not impose a network-level requirement, and the draft status matters. Adoption must continue across wallets and applications, while reviewers and registry operators must keep descriptors accurate as contracts evolve. Clear Signing has made understandable approvals possible today; ending blind signing will require that path to become the dependable default rather than an integration available only in supported cases.

Ethereum Clear Signing Is Live—but Blind Signing Is Not Over