Written by Pablo Gómez
Founder & CEO at Metlabs · Reviewed on October 11, 2026
It happens because many hardware wallets lack the semantic information to decode arbitrary contract functions: they can only show the raw hexadecimal and, to operate in DeFi, they often require enabling blind signing. The user must trust that the frontend is not compromised, that the RPC is not poisoned and that no one has swapped the destination address or the arguments. The standard solution is clear signing, which translates the raw data into a readable summary with the action, the recipient and the amount on the signer's screen.
Blind signing is the enabler of approval phishing: if the signer cannot see they are granting a permit or an infinite approve, they approve it. The ERC-7730 standard defines a machine-readable JSON format that describes in plain text what a contract's function calls and EIP-712 typed messages mean, enabling clear signing; it requires support on both sides, wallet and dApp, and if one is missing it falls back to blind signing.
Sources
Also known as
- blind signing





