What Makes a Wallet Cold
A wallet is cold when the private key that authorises a transaction has never existed on an internet-connected machine and never leaves the device it was generated on. That is the whole definition, and it is stricter than the way the word is usually used. A phone app that holds keys locally is self-custody, but it is not cold: the same operating system that stores the key also runs a browser, a messenger and whatever else you installed. Cold storage removes that shared surface entirely.
Three mechanisms do the work. First, on-device key generation: the seed is created by the device’s own entropy source and stays inside it, so no computer, no vendor and no cloud service ever sees it. Second, on-device signing: your laptop or phone builds an unsigned transaction, passes it to the device, and receives back only a signature. The key crosses no cable and no network. Third, physical confirmation: the device shows the destination address and amount on its own screen and waits for you to press a button. That screen is the security boundary that matters, because malware can rewrite what your browser displays but cannot rewrite what the device displays.
This is why hardware wallets defend against the two attacks that cost self-custody users the most. Key-extraction malware finds nothing to steal, because there is nothing on the host to find. Address-substitution malware, which swaps a pasted address for the attacker’s, gets caught the moment you compare what is on the small screen with what you intended, provided you actually read it. SatoshiLabs (Czechia) and Ledger SAS (France) both build around that model, and both ship Self-custody (non-custodial) designs where recovery depends on your backup rather than on the vendor.
Software wallets remain useful and belong in the same portfolio, just in a different role. Consensys (USA) builds MetaMask for Ethereum + all EVM chains; Snaps: SOL, BTC, Trust Wallet (Binance) covers 100+ chains incl. BTC, ETH, SOL, TON, and both connect to hardware for signing. Treat the hot wallet as a spending account and the cold device as the vault; our full wallet comparison covering security, coin support and custody models maps that split across the whole field.
Secure Element, Open Source and Air-Gap
Three properties get argued about most, and they pull against one another. A secure element is a tamper-resistant chip designed to keep secrets under physical attack, and its firmware is typically proprietary because the chip vendor requires it. Fully open-source firmware is auditable by anyone, which is a different and equally real kind of assurance. An air-gapped design never connects by cable or radio at all, exchanging transactions through QR codes or a memory card, which raises the security floor and lowers convenience. No mainstream device maximises all three, so the honest framing is a trade-off rather than a ranking.
| Wallet | Developer | Key storage | Air-gap / hardware signing | Price |
|---|---|---|---|---|
| Ledger | Ledger SAS (France) | Keys held inside a dedicated secure element chip; device firmware is proprietary | Not air-gapped: signs over USB, with Bluetooth on Nano X | From $79 |
| Trezor | SatoshiLabs (Czechia) | Open-source firmware; Safe 3 and Safe 5 add a secure element, Model One uses a general-purpose microcontroller | Not air-gapped: signs over USB | From $49 |
| Trust Wallet | Trust Wallet (Binance) | Keys encrypted in mobile operating-system storage on a connected device | Hot by design; hardware pairing support varies by chain | Free |
| MetaMask | Consensys (USA) | Keys encrypted inside the browser extension or mobile app | Hot by design; signs through a connected hardware device | Free |
| Exodus | Exodus Movement Inc. (US, NYSE: EXOD) | Keys stored locally on desktop, mobile or extension | Hot by design; supports hardware pairing for signing | Free |
| Phantom | Phantom Technologies (US) | Keys stored in extension or app storage on a connected device | Hot by design; hardware pairing on supported chains | Free |
Read the table as a spectrum of exposure rather than a scoreboard. The two hardware entries put a physical confirmation step between an attacker and your funds; the four software entries do not, which is why they suit day-to-day amounts and hardware pairing suits everything else. Note also that asset coverage differs sharply between the hardware options: Ledger lists 5,500+ supported assets across BTC, ETH, SOL + 100 chains, while Trezor lists 1,500+ across BTC, ETH + major chains. If you hold something outside a device’s support list, no amount of chip certification helps you.
Seed Backup and Passphrase Strategy
Your backup, not your device, is what actually holds your money. A device that is lost, bricked or confiscated costs you the hardware; a backup that is lost costs you the funds. Build the backup with that asymmetry in mind.
Write the recovery words by hand during setup and never photograph them, type them, or store them in a password manager, cloud note or email draft. Anything that has touched a networked device should be treated as compromised. Once the words are written, verify them by wiping the device and restoring from your own copy before you send it any meaningful amount. An unverified backup is an assumption, and people discover the transposed word years later at the worst possible moment.
Paper survives less than you think. Water, fire, damp basements and relatives clearing out a drawer are the realistic threats, so a metal backup is worth the modest cost for anything held long term. Store copies in at least two locations you physically control, far enough apart that one flood or fire cannot take both, and resist splitting words across locations unless you are using a scheme designed for it.
That scheme is Shamir backup, standardised as SLIP-39 and supported on Trezor devices. Instead of one phrase, it produces several shares and a threshold, so any sufficient subset restores the wallet and any smaller subset reveals nothing. It removes the single-point-of-failure problem that plagues a single sheet of metal, at the cost of a more complex process you must document for whoever comes after you.
A passphrase is the other lever, and it is genuinely powerful. Adding one produces an entirely separate wallet from the same recovery words, so the words alone no longer control the funds. It is a real second factor against a found or stolen backup. It is also unforgiving: there is no recovery, no hint and no confirmation that you got it right, only a different empty wallet if you did not. Store the passphrase separately from the words, never in the same container, and never rely on memory alone for a balance you cannot afford to lose.
Inheritance is the part people skip. Someone will eventually need to access this without you. Write instructions that explain what the device is, where the shares live, that a passphrase exists and how a trusted person obtains it, and store that document with your will or with a lawyer, keeping the secret material separate from the instructions.
Supply-Chain and Phishing Risks
Buy hardware from the manufacturer directly or from a distributor the manufacturer names on its own site. Marketplace listings, auction sites and second-hand devices are where tampered units surface, and the classic scam is a sealed-looking box containing a pre-printed card of recovery words with a note telling you to use them. No legitimate device ever ships with a seed. If words arrive in the box, the box is an attack.
On arrival, generate the seed yourself and let the device’s own attestation or vendor software confirm authentic firmware before you continue. If packaging or seals look reworked, stop and contact the manufacturer. A device you cannot verify is a device you should not fund.
Phishing is the larger threat in practice, because it scales. The recurring pattern is an urgent message claiming a data breach, a mandatory firmware update, a wallet migration or a security reset, pointing to a convincing site that asks you to enter your recovery phrase. There is no legitimate reason for any website, support agent or app to ask for those words. Vendor breaches have exposed customer contact details in the past, which is why these messages often use your real name and address and still lead nowhere good.
Practical defences: bookmark the vendor and wallet URLs and use only those, never a search-ad result. Verify firmware only through the official desktop application. Read every address on the device screen rather than the host screen, including the last characters. Treat unexpected tokens and airdrops as bait, since interacting with them is how malicious approvals get signed. Revoke stale token approvals periodically. Keep large balances on a device and separate address, apart from whatever wallet you connect to new applications, an approach we cover further in our review of privacy-focused wallet options.
How We Test and Rank Wallets
Our team buys each device at retail from the manufacturer and sets it up from a sealed box, recording the unboxing state, the firmware verification step and how clearly the setup flow explains the backup. We then perform the test that matters most: wiping the device and restoring it from the written words on a second unit, plus a restore into a compatible third-party client, so we know the backup is portable.
After that we send and receive on each major supported network, confirming that address display, fee controls and transaction details render legibly on the device screen. Hardware pairing is tested against desktop and mobile software wallets rather than assumed from a compatibility list, because a chain can be nominally supported and still fail at the signing step. Passphrase and Shamir workflows are exercised end to end, including deliberate mistakes, to see how the interface behaves when you get something wrong.
On the assurance side we record what is open source and independently reviewed versus what is proprietary, and we note the vendor’s disclosure history and how it has handled security research. Scores follow the weightings in the methodology block above this text. For single-chain readers we run the same protocol in our bitcoin wallet comparison.
How to Choose a Wallet
Let the amount and the recovery model drive the decision, not the feature list.
- Size the holding. If losing the balance would materially hurt, a hardware device is the baseline, and From $49 for Trezor or From $79 for Ledger is small against what it protects. For pocket-money balances, a free software wallet is proportionate.
- List the networks you need. Check them against the device’s coverage before buying. Ledger spans BTC, ETH, SOL + 100 chains, Trezor covers BTC, ETH + major chains, and on the software side Exodus reaches 50+ networks with 300+ assets while Phantom handles SOL + EVM + BTC.
- Split hot and cold deliberately. Decide which balance lives where before you fund anything, and keep the cold addresses out of any application you connect to.
- Choose your recovery model. A single phrase is simpler and easier to lose; Shamir shares are more durable and more work; a passphrase adds protection and removes your margin for error. Pick one you can execute reliably years from now.
- Confirm the software you already use pairs with it. If your daily interface is a Browser extension + mobile, self-custody setup like MetaMask, or a Mobile + extension, self-custody app like Trust Wallet, verify the hardware link works on the chains you actually transact on.
Buying two devices from different vendors is a reasonable hedge for larger holdings. What is not reasonable is buying a device, leaving the backup unverified, and assuming the chip has solved the problem.
Risks and Limitations
The blunt fact first: lose your recovery words and the funds are gone permanently. Not delayed, not recoverable through support, not retrievable by us or by the vendor. Self-custody moves the failure point from a company that might freeze your account to a backup that might be destroyed, and offers no appeals process in exchange. That trade is worth making only if you have actually built and tested the backup.
Hardware is not a solution to bad approvals. A device signs what you confirm, so if you approve a malicious contract interaction or a token allowance, the transaction is valid and irreversible. Cold storage protects the key, not your judgement, and the growing share of losses now comes from users authorising things they did not understand.
Vendors are also companies. Firmware can carry bugs, features can be added that you disagree with, optional recovery services shift part of the trust back toward third parties, and support databases have leaked customer details before, which fuels targeted phishing. Open-source firmware makes review possible without guaranteeing anyone has done it, and a secure element that resists physical attack cannot help if you are socially engineered.
Then the mundane risks. Devices are lost, damaged and forgotten; passphrases are misremembered; documented plans become obsolete as your holdings and family circumstances change. Estate access is a hard problem and most people leave it unsolved. Review your setup on a schedule, restore from your backup periodically to prove it still works, and keep the instructions current. A cold wallet is a practice, not a purchase.
This page is editorial information, not financial, tax or legal advice. Crypto assets are volatile and balances held with third parties are not bank-insured. Availability, fees and terms change — verify with the provider before you sign up.