If the company fails — recovering access and future‑proofing
Overview first: what happens if the company that made your hardware wallet goes bankrupt? Short answer: most of the time your crypto is still recoverable — provided you control the seed phrase, the derivation details, and any optional passphrase. (I believe this is the single most important point for long‑term holders.)
Why your crypto remains under your control
Hardware wallets are non‑custodial by design. That means private keys are derived from a seed phrase that you write down and control locally. The standards that make recovery possible are public:
Because these are standards, you can usually restore a seed phrase into any compatible wallet that implements the same standards. That interoperability is what keeps self‑custody future‑proof.
Step-by-step: recovering access if the manufacturer stops operating
Pause and check. Do not rush to move funds. If the company fails, take a breath and gather your records: the seed phrase, a note of whether you used a passphrase (25th word), and any recorded derivation path or account type.
Identify your seed type and length. BIP‑39 supports 12, 15, 18, 21 and 24 word phrases; manufacturers usually disclose which they use (see seed‑phrase). If you're unsure, check your original setup notes or packaging.
Check for an added passphrase. If you chose to use a passphrase (the optional 25th word), you must remember it exactly. The passphrase is not stored anywhere by the manufacturer (see passphrase (25th word)). Losing it means losing that derived wallet.
Find the correct derivation path. Different wallets (legacy, SegWit, native SegWit, Ethereum) use different derivation paths. Record or look up the path so addresses match the ones you control (see derivation‑paths and bitcoin‑guide).
Restore to a compatible wallet. Options include open‑source desktop or mobile wallets, another hardware wallet that supports your seed standard, or an air‑gapped restore tool (see third‑party‑wallets and air‑gapped). Restore in watch‑only mode first to verify address matches.
Verify addresses before moving funds. Generate a receiving address in the new client and compare it to the address you used previously. Send a small test amount first.
Consider moving funds after validation. Once addresses and balances match and you’re confident, move funds to a new setup if you prefer (for example, migrating to a multisig or a different hardware wallet).
(And test restores regularly — I test mine annually.)
Common compatibility pitfalls to watch for
- Proprietary seed formats: some devices may use vendor‑specific backup schemes. If your device used a non‑BIP‑39 format, restoration options can be limited.
- Shamir/SLIP‑39 parts: split backups are great, but SLIP‑39 is not universally supported. If you used Shamir shares, store the spec and tool references with your backup documentation (https://github.com/satoshilabs/slips/blob/master/slip-0039.md).
- Hidden wallets or passphrases: forget the passphrase and you lose access to that specific derived wallet.
- Companion app dependencies: if a wallet required an online service to derive addresses or sign firmware, you may need an alternative method (see firmware‑updates and verify‑firmware).
Sources: practical guidance from standards above and general wallet hardening advice (https://bitcoin.org/en/secure-your-wallet).
Options matrix: restore methods at a glance
| Method |
Pros |
Cons |
When to use |
| Restore to open‑source wallet (desktop/mobile) |
Fast, flexible, no manufacturer dependency |
Higher attack surface on host OS |
Temporary access, quick migrations |
| Restore to a different hardware wallet |
Keeps keys in secure element if supported |
Must match seed standard & path |
Long‑term replacement if compatible |
| Air‑gapped restore + PSBT signing |
Very secure, minimizes attack surface |
More complex workflow |
High‑value holdings or privacy needs |
| Multisig migration |
Distributes risk across devices/people |
Setup complexity, extra cost |
Long‑term institutional or family custody |
![Image: placeholder - metal backup plate example]
Future‑proofing: what to do today
- Record your seed phrase on a metal backup plate (see metal‑backup‑plates). Paper is fragile.
- Log the derivation path, coin types you used, and whether a passphrase was enabled. Put these notes in your secure backup (not with the seed itself).
- Test a restore on a spare device or an open‑source wallet every 6–12 months.
- Keep one copy of required documentation (spec URLs, SLIP‑39 instructions) with your backup so an heir or executor can follow them later (see inheritance‑planning).
But remember: write the passphrase nowhere if you rely on secrecy for security — store it securely if you must.
Multisig and other resilience strategies
Multisig (multi‑signature) spreads control of funds across multiple keys. That means the failure of any single manufacturer or company doesn’t block access. Multisig setups use standards (like PSBT, BIP‑174) and are supported by many wallets; see multisig and multisig‑compatibility.
In my experience, a 2‑of‑3 multisig using devices from different manufacturers and an air‑gapped signer gives a good balance of usability and resilience.
FAQ — real user questions answered
Q: Can I recover my crypto if the company goes bankrupt?
A: Yes — if you control the seed phrase and have the derivation details, you can usually restore to a compatible wallet. Standards like BIP‑39 and BIP‑32 enable this (https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki).
Q: What happens if the company stops providing firmware updates or app support?
A: Your private keys remain yours. You may lose convenience features and signed firmware checks, but you can restore the seed into other compliant wallets. See firmware‑updates and verify‑firmware for steps to protect yourself.
Q: What if I used Bluetooth or cloud features? Is that a risk if the company collapses?
A: Bluetooth and cloud features are convenience channels. If those services disappear, you can still restore via the seed phrase using wired or air‑gapped methods (see connectivity‑usb‑bluetooth‑nfc).
Conclusion and next steps
If the company behind your hardware wallet fails, the most reliable recovery path is your seed phrase plus accurate metadata (derivation path, passphrase use). I recommend: secure a durable seed backup, record derivation details, test a restore, and consider multisig if you want extra resilience.
Ready to prepare? Start with the step‑by‑step restore checklist in Restore & recovery, review seed phrase management, and read about multisig to harden your plan.
(And if anything feels unclear, test a mock restore on a spare device — practice prevents panic.)
