Recovery Kit
Last updated: 2026-07-09
A seed phrase is not always the whole recovery plan. For singlesig it may be enough. For passphrases, multisig, and watch-only wallets, you also need the context that tells future-you what those words are supposed to unlock.
What belongs in a Bitcoin recovery kit?
A Bitcoin recovery kit should include seed backups, passphrase instructions if used, each wallet fingerprint, derivation path, output descriptor or wallet file, device model, wallet app, test date, and emergency instructions. Store secrets separately from metadata. A thief should not get everything from one envelope.
| Item | Secret? | Why you need it |
|---|---|---|
| Seed words | Yes | Recreates private keys |
| Passphrase | Yes | Unlocks the real wallet if used |
| XFP | No | Confirms you restored the right wallet |
| Derivation path | No | Helps wallet software find addresses |
| Output descriptor | Usually no | Rebuilds watch-only and multisig wallets |
| Instructions | No | Prevents panic and guessing |
Seed Words
Stamp seed words on metal. Keep at least two copies in separate places. Do not keep both where the same fire, flood, theft, or family dispute can take them.
Do not photograph the words. Do not type them into a computer to “make a backup.” If you already did, make a new wallet and move the funds.
Passphrase Status
Write down whether a passphrase exists. That line alone can prevent disaster.
You have three choices:
- No passphrase.
- Passphrase used, stored separately.
- Passphrase used, known by a specific person or procedure.
Do not leave heirs guessing. A passphrase is not a hint. It is part of the wallet.
XFP: The Quick Sanity Check
The extended fingerprint, or XFP, is a short identifier for the wallet. Write it on your recovery notes and, if your setup allows it, on the metal plate near the seed label.
After a restore, check the XFP before receiving or sending. If the XFP is different, stop. You are in a different wallet.
Derivation Path and Address Type
Most modern Bitcoin wallets use standard paths, but do not rely on memory. Write down the address type and path:
- Native SegWit:
m/84'/0'/0' - Taproot:
m/86'/0'/0' - Multisig Native SegWit: often
m/48'/0'/0'/2'
If that looks like gibberish today, fine. Your wallet app understands it. Future recovery may depend on it.
Output Descriptor or Wallet File
For multisig, the descriptor is as important as the seeds. It tells the wallet which keys belong together and how many signatures are needed.
Export the wallet descriptor from Sparrow or your coordinator and store it in more than one place. It does not usually contain private keys, but it does reveal wallet structure and addresses. Treat it as private metadata.
For singlesig watch-only wallets, export the watch-only file or descriptor too. It makes recovery cleaner.
Device and Software Notes
Write down the device and software used:
- COLDCARD Q or Mk5
- Cove, Sparrow, Nunchuk, or other wallet app
- Address type used
- Date you tested recovery
- Where to find the latest version of the wallet app
Do not write “use my laptop.” Laptops die. Write the process.
Emergency Instructions
Your instructions should fit on one page. No jargon if your family is not technical.
Use plain lines:
- Do not enter seed words into a website.
- Do not respond to people who contact you first.
- Contact this person before moving funds.
- Use this wallet app to restore watch-only information.
- Send a small test transaction first.
If your plan needs a 40-page binder, it will fail under stress.
Storage Pattern
Do not put every component in one box.
A simple pattern:
- Metal seed copy A: home safe or trusted local location
- Metal seed copy B: different physical location
- Passphrase: separate sealed envelope or legal document
- Descriptor and instructions: with estate papers or encrypted digital copy
- Contact list: printed and updated yearly
Review it once a year. If you moved, changed wallet apps, added a passphrase, or created multisig, update the kit that week.