{"id":72668,"date":"2026-09-18T21:12:59","date_gmt":"2026-09-18T18:12:59","guid":{"rendered":"https:\/\/lwallet.com.ua\/?p=72668"},"modified":"2026-09-18T21:12:59","modified_gmt":"2026-09-18T18:12:59","slug":"clear-signing-blind-signing","status":"publish","type":"post","link":"https:\/\/lwallet.com.ua\/en\/clear-signing-blind-signing\/","title":{"rendered":"Clear Signing vs Blind Signing: how to know what you\u2019re actually signing"},"content":{"rendered":"\r\n\r\n\r\n

A hardware wallet protects your private key, but that does not mean its screen will always tell you, in plain language, exactly what you are signing<\/strong>. When you use a dApp, the browser may show a familiar action \u2014 a transfer, swap, or approve<\/code> \u2014 while the hardware wallet receives the underlying transaction data. If the device cannot decode that data, you may be left with a hash, raw data, or a generic warning. That gap is what Clear Signing<\/strong> is designed to address.<\/p>\r\n\r\n\r\n\r\n

The consequences are easy to see in the Radiant Capital and Bybit incidents. At Radiant, malware compromised the computers of at least three developers. The signers saw the transaction they expected on screen, but the infected machines altered the data before it reached the hardware wallets. They ultimately produced three valid signatures for a malicious transaction, and roughly $50 million<\/strong> was drained from the protocol.<\/p>\r\n\r\n\r\n\r\n

The Bybit incident involved a different compromise of the environment used to manage its multisig cold wallet. Malicious JavaScript misled the signers about the transaction they were approving: instead of a routine transfer, they authorized a change to the logic of the multisig cold wallet. The attacker then moved roughly $1.46 billion<\/strong> in assets. The attacks were technically different, but they exposed the same problem: the interface on your computer cannot be treated as the final source of truth<\/strong>. Below, we will look at what Clear Signing actually verifies and what you should check on the device before you approve a request.<\/p>\r\n\r\n\r\n\r\n

What a hardware wallet actually signs<\/h2>\r\n\r\n\r\n
\r\n
\"Clear<\/figure>\r\n<\/div>\r\n\r\n\r\n

When you use a dApp, the transaction is first prepared by software on your computer or phone \u2014 Ledger Wallet, Trezor Suite, MetaMask, Rabby, or another interface connected through WalletConnect, for example. The transaction data is then sent to the hardware wallet, where the private key signs it.<\/p>\r\n\r\n\r\n\r\n

The hardware wallet does not see the website itself.<\/strong> It does not know what the browser button says or which address you just checked on your monitor. That is why the device screen is there for more than approving a request: it is where you verify the operation the device is actually being asked to sign.<\/p>\r\n\r\n\r\n\r\n

Before getting into Clear Signing, it helps to separate a few concepts that are often mixed together:<\/p>\r\n\r\n\r\n\r\n