A hardware wallet may keep private keys isolated from an internet-connected computer, yet if the recovery phrase is photographed, stored in cloud notes or copied into an email, much of that protection disappears. Anyone who obtains the phrase can usually recreate the wallet without needing the original device.

For me, the first rule is keeping the recovery phrase completely offline. Writing it on paper is still common, but paper has obvious weaknesses: fire, water, physical damage and deterioration over time. Metal backup solutions can reduce those risks, especially for long-term storage.

Physical location matters just as much as the material. Keeping the hardware wallet and its recovery phrase together creates a single point of failure. A burglary, fire or other local incident could compromise both at the same time. Separating the device and backup can provide significantly better resilience.

The challenge is avoiding excessive complexity. Splitting a seed phrase into several handwritten fragments may sound safer, but poorly designed backup schemes can make recovery much harder. If one piece is lost or the owner forgets how the system works years later, additional security has actually created additional risk.

Some users consider multiple geographically separated backups. That can protect against physical disasters, but every additional copy also increases the number of places where the recovery phrase could potentially be discovered. There is a real trade-off between redundancy and exposure.

Passphrases can provide another security layer, but they also introduce another secret that must be remembered or backed up correctly. Losing the passphrase while retaining the seed phrase can still make the intended wallet inaccessible.

For larger holdings, multi-signature setups can reduce dependence on a single seed phrase altogether. Instead of one backup granting complete access, several independent keys may be required to move funds. That can improve security, but it also requires much more careful planning and testing.

Whatever method is used, I think recovery should be tested before significant funds are stored. A backup that has never been verified is only an assumption.

How do you back up your hardware wallet?

Do you prefer paper, metal seed storage, geographically separated backups, passphrases or multi-signature custody?

And where do you think the right balance is between having enough redundancy to recover your wallet and creating too many copies of sensitive recovery information?

In general, ignoring firmware updates for years is not a good strategy. Security flaws can be discovered over time, and manufacturers may release fixes that protect against newly identified attack methods or improve device reliability.

At the same time, I do not think every update needs to be installed the moment it appears. For users storing significant amounts of crypto, it can make sense to wait briefly, review the release notes and confirm that there are no widespread reports of problems before updating a critical device.

The most important step is verifying that the update comes from the official wallet software or manufacturer channel. Fake firmware updates, phishing pages and malicious applications are a real threat. A legitimate update should never require you to enter a recovery phrase into a website or random application.

Backups also matter. Before updating, users should already have a verified recovery phrase stored securely. Firmware updates are usually designed to preserve wallet access, but long-term self-custody should never depend on one physical device remaining functional forever.

I also think frequency depends on how the wallet is used. A device connected regularly to DeFi applications and third-party wallets may benefit from staying more current than a hardware wallet that remains offline and is only accessed a few times per year.

Another consideration is compatibility. Wallet software, operating systems and blockchain networks evolve. Very old firmware can eventually create connection or transaction-signing problems even if there is no immediate security issue.

For me, the best approach is to treat firmware updates as part of routine wallet maintenance: monitor important releases, verify the source, read what changed and update deliberately rather than automatically clicking every notification.

How often do you update your hardware wallet firmware?

Do you install updates immediately, wait a few days for community feedback or only update when there is a major security fix?

And what checks do you perform before updating a device that holds significant crypto?

The main advantage of a hardware wallet is that private keys stay isolated from an internet-connected computer or phone. That significantly reduces exposure to malware, browser extensions, phishing pages and other attacks that target software wallets.

For long-term holders, that separation can be extremely valuable. If someone is not actively trading or interacting with DeFi every day, keeping the majority of funds offline can remove a large number of unnecessary attack surfaces.

The biggest weakness is still the human factor. A hardware wallet can be secure, but the recovery phrase can be stored badly, photographed, uploaded to cloud storage or exposed during a fake recovery process. In many real-world cases, the device itself is not what fails — the backup procedure does.

Another issue is operational complexity. Firmware updates, device verification, PIN management and recovery testing all require some level of technical confidence. Users who do not understand those processes can still make mistakes even with strong hardware.

I also think it is important to separate long-term storage from daily activity. Connecting a hardware wallet to every dApp or signing frequent transactions can reduce some of the security advantage. A cleaner setup is often to keep long-term holdings in cold storage and use a separate wallet for active Web3 activity.

Multi-signature setups can provide another layer of protection for larger portfolios, but they also increase complexity. For some users, a simple hardware wallet with a well-protected backup may actually be safer than an advanced setup they do not fully understand.

There is also the question of physical security. Devices can be lost, damaged or stolen. That is why the recovery process is just as important as the wallet itself. A long-term storage strategy should assume that the physical device may eventually become unavailable.

So are hardware wallets still the safest option for long-term crypto storage?

Do you trust a single hardware wallet setup, or do you prefer multi-signature, multiple devices or geographically separated backups?

And what do you think creates the biggest risk in cold storage today — device security, seed phrase storage, phishing, firmware updates or user error?

The interesting part is that choosing between them is not only about which device supports more assets. The decision usually comes down to security architecture, software experience, recovery options, ecosystem support and how much trust you are comfortable placing in the manufacturer’s design decisions.

Ledger is often attractive to users who want broad asset support and a polished ecosystem around hardware storage. For people managing several cryptocurrencies, compatibility can be a major advantage because it reduces the need to maintain multiple devices or wallet setups.

Trezor tends to appeal strongly to users who value transparency and a relatively straightforward approach to self-custody. For some holders, being able to understand more about how the wallet works is just as important as convenience.

But I think the real comparison should go deeper than brand reputation.

A hardware wallet is only one part of the security setup. Seed phrase storage, firmware updates, device verification and how the wallet is used with third-party applications can all introduce risk. Someone using an excellent hardware wallet with a poorly protected recovery phrase is not necessarily safer than someone using a simpler device with disciplined operational security.

Software experience also matters more than people sometimes admit. If the companion application is confusing or transaction details are difficult to verify, users are more likely to make mistakes. Hardware wallets should make self-custody safer without making basic transactions unnecessarily difficult.

Another consideration is how much crypto you actually plan to manage. Someone holding primarily Bitcoin may have very different requirements from a user who regularly interacts with Ethereum, Solana, DeFi and multiple token ecosystems.

I also think redundancy becomes important once the value stored is significant. Depending on one physical device without a tested recovery procedure creates unnecessary risk. The most important question may not be which wallet you buy, but whether you could safely recover everything if that device disappeared tomorrow.

If you had to choose between Ledger and Trezor today, which would you pick?

What matters most to you — security architecture, supported cryptocurrencies, open-source components, user interface, recovery options or third-party wallet compatibility?

And for people who have used both, which one has been more reliable for long-term self-custody?