Clear signing makes a transaction readable, but the description still needs trust

An Ethereum working group announced a clear-signing initiative on 12 May, involving wallet developers, security firms and the foundation’s security programme. Its objective is to show people structured, understandable descriptions of the transactions they approve. The foundation is supporting the registry infrastructure, while independent reviews and attestations help assess descriptors. Wallets choose which descriptor sources they trust. The arrangement can cover existing applications because the descriptions sit alongside transactions rather than requiring every contract to be rewritten. Source.

ERC-7730 defines a JSON format for displaying smart-contract calls and typed messages. It adds context to data that is otherwise difficult to interpret: an integer may need a token’s decimals and ticker, while a function name may not explain the user’s intended action. The specification remains marked Draft in the source reviewed for this article. Its security considerations include binding the description to the right context and protecting registries against misleading entries. A readable sentence is only helpful if it accurately describes the data being signed. Source.

Our interpretation is that clear signing improves an important decision point without removing the need to make a decision. A confirmation should explain what moves, who receives it and what authority remains after the action. If the wallet cannot verify the relevant description, it should make that uncertainty visible. Product teams also need to test how a small device presents a long or unusual transaction. Better formatting cannot rescue a misleading descriptor, and a technically accurate screen can still be confusing. The useful measure is whether the person can identify the consequential action before authorising it, including when the surrounding application has been compromised.

A simple test is to show a confirmation to someone who did not build the application and ask them to explain the permission in their own words. Do they understand whether they are approving one transfer or an ongoing allowance? That exercise checks comprehension; it should accompany technical validation of the descriptor, rather than replace it.