An open recovery folder, signing device, blank steel backup plate and sealed envelope, editorial illustration
Security / GUIDE

A backup is a plan you have tested

Rehearse recovery without turning an ordinary check into an emergency.

Start reading
5 min readEnglish

Related walkthroughs

READING MODE

Define what the rehearsal proves

A written backup is reassuring, but a useful test answers a specific question: can this material recover the wallet I expect? There are several separate checks. You might be testing whether the words are correct, whether a opens the right wallet, whether the wallet configuration is complete, or whether another person can follow your instructions.

Do the smallest test that answers the question. A supported dry-run backup check is often a sensible first step. It avoids deliberately destroying your working setup. Read the instructions for your exact device before starting, and do not erase your only functioning signer just to see what happens.

Watch Twelve words: where a seed comes from, explained in 2 minutes. Captions available.
BIP39 wallets
Passphrases
Splitting a seed: Seed XOR and Shamir

Make a recovery inventory

Record the wallet application, backup standard, account or address type, and whether an extra passphrase is required. A multisignature wallet also needs its wallet configuration, including the spending policy and cosigner public information. A label saying “Bitcoin backup” is less useful than a clear explanation of which wallet the material belongs to.

Keep the inventory separate from the secrets. It should tell you what exists and how to find authorized instructions, not become a second copy of every key. If you use several accounts or wallet types, include each in the scope of the test. Restoring one address does not automatically demonstrate recovery of everything you own.

Choose the right level of testing

A device’s backup-check function can confirm that its stored secret matches the recovery material. It may not test optional passphrases or additional wallet configurations. For a passphrase wallet, use the project’s documented verification process and compare a known receive address. Never paste a real seed or passphrase into a website to check it.

A fuller recovery rehearsal can use a suitable spare device and the manufacturer’s procedure. Plan where the device and backup will be handled, how you will verify the resulting wallet, and how the spare will be secured afterwards. A spare restored signer contains spending authority; treat it as such.

Write down the result, not the secret

Your record might say: “Checked backup on 12 November; passphrase wallet matched the expected address; configuration export readable.” If the test fails, keep the existing working setup intact while you investigate the exact mismatch. Avoid repeated improvisation or following recovery instructions from someone who contacts you unexpectedly.

Revisit the plan after meaningful changes: a new wallet, changed passphrase, altered policy, moved backup location or a change in the person expected to help. There is no prize for checking constantly. The point is a current, understandable recovery process that reduces uncertainty when a device breaks.

Set aside uninterrupted time for the exercise. Stop if you feel rushed or cannot explain the next action. Recovery practice is most valuable when it replaces assumptions with specific, recorded observations.

  • Identify the wallet and the question being tested.
  • Use the supported check before considering a reset.
  • Verify the expected wallet, not just valid-looking words.
  • Record the date, result and next action without secrets.

If a backup or device is exposed

A lost phone, a stolen signer and recovery words entered into a fake website are different incidents. Establish what an attacker may have: a locked device, public wallet data, one multisig key, or enough secrets to spend. Do not share those secrets while seeking help.

If spending secrets may be exposed, restoring the same seed or changing the device PIN does not revoke the attacker’s access. Use the wallet maker’s migration procedure to create an independent wallet with fresh secrets on trusted equipment. Verify its backup and receiving address, then move affected funds with appropriate urgency; do not erase the only working signer first.

For multisig, identify the threshold and which keys remain trustworthy. A single exposed key may not permit theft, but it weakens the arrangement. Replacing a signer in an app does not change existing outputs: funds must move to the new policy. Follow the coordinator’s documented procedure.

Stop reusing exposed deposit addresses and update payment instructions. Keep transaction records without secrets. If funds have already moved without permission, recovery is not guaranteed; a stranger promising reversal for a fee or asking for your seed is not a recovery mechanism.

Valid words, but an empty wallet

Keep any working device intact. Confirm the recovery format and intended network, and let the wallet finish synchronising. Valid-looking words do not prove that you restored the intended wallet. Compare a known receiving address privately, rather than publishing an to ask for help.

Check whether the original wallet used a BIP39 passphrase. Capitalisation, spaces and spelling matter; a different passphrase can open an empty wallet without an error. The app password and device PIN are not substitutes. Use the wallet’s supported entry and checking procedure.

Next check account number, address/script type and derivation settings against your recovery inventory. A wallet may need to scan additional accounts or extend its address gap limit to find previously used addresses. Follow its documentation instead of trying arbitrary paths or changing every setting at once.

A multisig restore also needs the policy and cosigner information. Lightning recovery can need channel state or the implementation’s recovery service; an on-chain balance appearing does not prove channel funds are recovered. If uncertainty remains, keep the working setup and consult official support without disclosing secrets.

Continue your path

One question leads to another.

01Verify the software before you trust it02The complete multisig recovery kit03Coldcard

Find your next answer.

Search the complete field guide · Esc to close