Hardware wallets: what they protect and what they do not

The security boundary

A hardware wallet aims to keep signing keys isolated even when connected to a compromised computer. It displays critical transaction details so the user can verify them on a trusted screen. <strong>Threats remain.</strong> A device cannot save a seed phrase entered into a phishing site, an address ignored on-screen or a malicious recovery process. Supply-chain checks, authentic firmware and careful verification still matter.

<strong>Set up deliberately.</strong> Buy from a source you can evaluate, initialize the device yourself, record the generated backup offline and verify a receiving address on the device. Send a small test, then rehearse recovery before scaling up.

Inspect a payment on both screens

Suppose malware on a laptop replaces a copied recipient address. The laptop may show the address you intended while sending a different one to the hardware wallet. The protection works only if the device displays the actual destination it is being asked to sign and you compare that display with an independently verified instruction.

Approving without reading converts the device into an expensive confirmation button. Use the same discipline during setup and recovery. Initialize the device yourself, confirm how firmware authenticity is checked, record the backup offline, and reject any package containing a prewritten phrase. Send a small test and verify the receiving address on the device.

A hardware wallet narrows the signing attack surface, but the user, backup, supply chain, and recovery process remain part of the security system.

What happens when you sign

Your computer or phone builds an unsigned transaction and passes it to the device, typically as a partially signed Bitcoin transaction. The device checks it, shows the destination address and amount on its own screen, and waits for you to confirm with a button. Only then does it sign, inside its own chip, and hand back a signed transaction for the computer to broadcast.

The private keys never leave the device. A compromised computer can lie about what it wants signed, which is why reading the device screen - not the computer screen - before pressing confirm is the whole security model.

Choosing one

Prefer a device with a screen large enough to show a full address, open-source firmware you or others can audit, a secure element or an equivalent design for key storage, and a manufacturer with a track record of disclosing and fixing vulnerabilities. Air-gapped models that communicate by QR code or SD card remove the USB connection entirely.

Multi-asset support is a convenience with a cost in attack surface; Bitcoin-only firmware exists for several devices. Buy new, from the maker or an authorised reseller, and generate the recovery phrase on the device yourself. Price differences between models are small next to the amounts they protect.

Living with it

The device is a signer, not the backup: the recovery phrase is. Test restoring the phrase on a second device or in software with a small balance before relying on it. Update firmware from the official app and verify what it asks you to confirm.

Do not enter the phrase into the manufacturer's app, website or support chat - the device has it and does not need it again, and no legitimate support request involves it. Keep a note of the derivation path and address type so a different wallet can find your coins years from now.

For larger holdings, two devices from different makers in a two-of-three multisig removes the single point of failure.