In this article
- TL;DR
- The Question Everyone Gets Wrong
- Scenario A Seed Lost Wallet File Present Forgotten Password
- Scenario B Seed Lost Device Lost or Wiped No Backup
- Scenario C 23 of 24 Seed Words Known
- Scenario D Passphrase Forgotten Seed Remembered
- Scenario E Hardware Wallet PIN Locked
- Scenario F Forgotten BIP Standard 44 49 84 86
- Scenario G Mnemonic Not on the BIP-39 Word List
- Scenario H Heir Has Hardware Wallet No Seed
- Professional Recovery Services in 2026
- Recovery Scenario Decision Matrix
- What to Do After Recovery
- Preventing the Next Loss
- Recovery Services Are Legitimate but Verify Everything
- Disclaimer
TL;DR
I work in the crypto self-custody space, and wallet recovery is not one problem. It is eight scenarios, each with a different tool and a different chance of success. The section that matches your situation is the only one you need. Read it, judge the odds, then decide between DIY and a recovery service. If you are the heir in scenario H, read that section before you touch the device, then the Bitcoin estate planning guide.
The Question Everyone Gets Wrong
The question I hear most often is not "how do I recover my wallet." It is "is there any way to recover my wallet," asked by someone who already suspects the answer is no and hopes I will say otherwise.
Some of these problems take minutes. Some take hours with the right tool. Some cannot be solved at all. The cryptography that keeps a thief out of your wallet also keeps you out once the seed is gone.
A Bitcoin private key is a number below the order of the secp256k1 curve, about 1.16 times 10 to the power of 77, and SEC 2 rates the curve at 128 bits of security (SEC 2, section 2.4.1 and table 1). No computer that exists can search that space. Any service that promises to recover Bitcoin from an address alone, with no seed, no wallet file and no device, is lying to you.
Eight scenarios below map to eight real recovery paths. Find yours.
Scenario A Seed Lost Wallet File Present Forgotten Password
This is the most recoverable scenario. You hold the encrypted wallet file (a Bitcoin Core wallet.dat, an Electrum wallet file, a Blockchain.com wallet backup, a MetaMask vault, or a MultiBit wallet) and you remember fragments of the password. You do not need the seed phrase, because the keys sit inside the encrypted file.
Use btcrecover, which supports all five. Pick the 3rdIteration fork, not the original gurnec repository, whose last commit is dated 21 December 2017 (gurnec/btcrecover). Write a token list of every fragment you remember and let btcrecover combine them, with typos and capitalisation variants, until one combination decrypts the file.
Bitcoin Core encrypts wallet keys with AES-256-CBC, using a key derived by repeated SHA-512 hashing that mimics OpenSSL's EVP_BytesToKey (crypter.cpp). The round count is at least 25,000 (crypter.h) and is tuned so one guess takes about 100 ms on the machine that encrypted the wallet (wallet.cpp). btcrecover's own benchmark tests about 70 Bitcoin Core passwords per second on an Intel i7-8750 CPU and about 6,750 per second on an NVIDIA 1660 Ti GPU (btcrecover GPU guide). Brute force is slow. If you remember most of the password, the search still finishes. The full setup sits in the btcrecover tutorial.
Run everything on an offline machine. My rule: make three copies of the wallet file before any command runs, work only on a copy, and keep --autosave on throughout.
Scenario B Seed Lost Device Lost or Wiped No Backup
Stop. There is no recovery path here.
The private keys come from the 24-word (or 12-word) seed generated at device setup. If you never wrote the seed down, or the backup is gone, and the device itself is lost or has wiped itself, the keys are gone. There is no encrypted file to attack and no partial information to search from.
Some recovery services will take your money anyway. The FBI warns that fake recovery firms charge an up-front fee, then go silent or ask for more (FBI IC3, 11 August 2023). Without the seed or the device, no process can derive the private key.
The lesson, which applies before the loss happens, lives in Bitcoin self-custody. In my view, seed phrases go on steel, in duplicate, in separate places, on the day you set up the wallet, not a week later.
Scenario C 23 of 24 Seed Words Known
Highly recoverable, and faster than most people expect.
A 24-word BIP-39 seed holds 256 bits of entropy plus an 8-bit checksum taken from the SHA-256 hash of that entropy (BIP-39). If you know which word is missing, there are 2048 candidates for that slot, and only about 1 in 256 of them passes the checksum. If the missing word is the last one, 8 candidates pass, because that word carries only 3 bits of entropy. seedrecover.py tests the survivors against an address from your wallet, and the project's examples for one missing word find the seed almost straight away (btcrecover seed examples).
You need two things: the 23 words you have, and one public address from that wallet, ideally one of the first it created. If you have no address and no xpub, an address database (a file of every address that has appeared on the blockchain) stands in for it, at the cost of downloading the chain and building the file (btcrecover AddressDB guide).
python seedrecover.py \
--wallet-type bip39 \
--mnemonic "word1 word2 ... word22 word23" \
--addrs bc1q... \
--addr-limit 5
Two missing words raise the search to 2048 × 2048, about 4.2 million combinations. Three missing words raise it to about 8.6 billion. btcrecover's benchmark for a 24-word seed is about 160,000 candidates per second on an Intel i7-8750 CPU (btcrecover GPU guide). At that rate two known gaps take under a minute and three take about 15 hours. If you do not know where the gaps are, multiply by the number of possible positions.
Scenario D Passphrase Forgotten Seed Remembered
A BIP-39 passphrase (the so-called 25th word) is a separate secret on top of the mnemonic. BIP-39 says every passphrase generates a valid seed, but only the correct one opens the wallet you funded (BIP-39). If you used a passphrase and forgot it, your funds sit in the passphrase wallet, not the base wallet.
It is recoverable if you remember fragments. Run btcrecover with the --bip39 option (btcrecover tutorial):
python btcrecover.py \
--bip39 \
--mnemonic "your 24 words here" \
--addrs bc1q... \
--addr-limit 10 \
--tokenlist tokens.txt
The token list works the same way as for password recovery. List every fragment, capitalisation variant, number pattern and symbol you might have used. Your memory sets the size of the search.
If you remember nothing about the passphrase, it cannot be recovered. BIP-39 runs the mnemonic and passphrase through PBKDF2 with 2048 rounds of HMAC-SHA512, and no inverse operation recovers the passphrase from the addresses. The BIP-39 brute force attack post covers the math in depth.
Scenario E Hardware Wallet PIN Locked
Too many wrong PINs erase the wallet from the device. Trezor erases it after 10 wrong attempts on the Safe 7 and after 16 on other models (Trezor). Ledger resets to factory settings after 3 (Ledger support). A Coldcard bricks itself for good after 13 failed attempts (COLDCARD docs), so you will need a new device. With the seed phrase backup in hand, none of this costs you a single satoshi.
The seed phrase is the wallet. The device is the interface to it. Any device that supports the same backup standard restores the same keys from it, and btcrecover lists Trezor, Ledger and Coldcard among the BIP-39 wallets it supports (btcrecover). Pick "restore" on first boot, enter the words in order, and your wallet is back.
Check your backup format first. Trezor Safe devices and the Model T have made a 20-word SLIP-39 Single-share Backup by default since June 2024 (Trezor), and that backup restores only on a device that supports SLIP-39.
If you also set a BIP-39 passphrase on the original device, enter it during restoration. Without it, the restored wallet shows a different, empty wallet, because the passphrase derives different addresses.
PIN-lock recovery needs no extra tool. The seed phrase is enough. The only complication is a lost seed backup (see Scenario B).
Scenario F Forgotten BIP Standard 44 49 84 86
BIP-44, BIP-49, BIP-84 and BIP-86 define different derivation paths and address formats from the same seed phrase. They produce different addresses.
- BIP-44: Legacy P2PKH addresses starting with
1, pathm/44'/0'/0' - BIP-49: Nested SegWit P2SH-P2WPKH addresses starting with
3, pathm/49'/0'/0' - BIP-84: Native SegWit P2WPKH addresses starting with
bc1q, pathm/84'/0'/0' - BIP-86: Taproot P2TR addresses starting with
bc1p, pathm/86'/0'/0'
If you funded an address under one standard and restore under another, the balance shows as zero. Your Bitcoin is not lost. It sits at a different derivation path on the same seed.
The fix needs no special tool. Sparrow Wallet offers exactly these four script types (Sparrow's ScriptType.java). Import your seed with the script type set to "Legacy" and check for a balance. If it is zero, switch to "Nested Segwit" and check again. Continue through Native Segwit and Taproot. Electrum's BIP-39 account detection tries 18 path and script combinations, none of them Taproot (Electrum's bip39_wallet_formats.json). You are only finding which branch of the derivation tree holds your funds.
Some wallets use non-standard account numbers or paths. If the four standard paths all show zero, check the original wallet software's documentation for its default derivation path.
Scenario G Mnemonic Not on the BIP-39 Word List
This scenario has no good outcome if you do not know the original wallet software.
The BIP-39 English word list is the 2048-word set at github.com/bitcoin/bips/blob/master/bip-0039/english.txt. If your mnemonic contains words not on that list, a different system generated it.
Common systems that use their own word lists:
- A 20-word Trezor Single-share Backup, built on SLIP-39 with a list of 1024 words (Trezor)
- Electrum before version 2.0, with a 1626-word list (Electrum
old_mnemonic.py)
One trap runs the other way. Electrum 2.0 and later seeds use words from the same English list, but Electrum does not generate BIP-39 seeds (Electrum Seed Version System). Such a seed passes the word check below and still fails in a BIP-39 wallet. Restore it in Electrum.
If you know which software generated the seed, install that software and use its own restore flow. btcrecover's seedrecover.py also handles Electrum 1.x, Electrum 2.x and SLIP-39 seeds (btcrecover). If you do not know the software, no single tool covers every proprietary scheme.
Check whether your words appear in the BIP-39 list before you spend time on BIP-39 tools:
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0039/english.txt | grep -Fx "yourword"
If a word is absent, stop the BIP-39 toolchain.
Scenario H Heir Has Hardware Wallet No Seed
The heir here inherits an estate-planning failure first and a recovery problem second.
The device still holds the wallet. If the heir knows the PIN, the heir can open the device and send the funds to a new wallet the heir controls. If the heir does not know the PIN, every wrong guess counts toward a wipe: 3 on a Ledger (Ledger support), 10 or 16 on a Trezor (Trezor), 13 on a Coldcard (COLDCARD docs). After a wipe without a seed backup, the funds are gone. Do not guess.
Physical extraction is not always impossible. Kraken Security Labs extracted the seed from a Trezor One and a Trezor Model T in 2020 with 15 minutes of physical access (Kraken). That was a lab attack on two older models. Treat any firm that offers "chip extraction" for your exact device with the scepticism of Scenario B.
If you are the heir in this situation, you are facing the outcome of a self-custody setup that did not include an access plan. Bitcoin holders who want to spare their own heirs should read the Bitcoin estate planning Switzerland guide. It covers sealed executor envelopes, SLIP-39 Shamir share distribution, notary deposits and annual recovery drills.
Professional Recovery Services in 2026
Three operators publish their history and fees on their own sites and take cases where DIY tools fall short.
- Wallet Recovery Services (walletrecoveryservices.com): in operation since 2013, 20 percent of the wallet's value, payable only on success
- KeychainX (keychainx.com): recovering wallets since 2017, 20 percent success fee, covers Bitcoin and Ethereum wallet passwords, MultiBit, Electrum, Blockchain.com and hardware-wallet seed problems
- Crypto Asset Recovery (cryptoassetrecovery.com): since 2017, 20 percent of the wallet's liquid assets, withdrawn on-chain only after a successful recovery
All three work from your wallet file or your seed words. Wallet Recovery Services says so directly: if they decrypt your wallet, they could steal the money in it. Crypto Asset Recovery takes its fee by withdrawing it from the recovered wallet itself. You are trusting the firm with your funds. Vet each operator independently before you engage. In my view, run these checks:
- You pay nothing up front. The FBI warns that fake recovery firms take an up-front fee and disappear (FBI IC3).
- The fee is a percentage of recovered funds, stated on the firm's own site.
- The firm has a verifiable public history: a real address and contact details, not a Telegram username.
- You found them yourself and checked the domain. The FBI notes that fake recovery firms also advertise in search results and social media, so a search hit is not proof.
For Ordinals-bearing outputs, recovery follows the same path as regular Bitcoin. Inscribed sats sit in normal Bitcoin outputs (ord inscriptions docs). Recover the seed or private key, then use the ord client, which does sat control, to move inscriptions. The ord wallet documentation at docs.ordinals.com covers restoring an ord wallet from its mnemonic.
Recovery Scenario Decision Matrix
The probabilities in this table are my own estimates, built from the sections above.
| Scenario | You Have | Recovery Probability | Tool |
|---|---|---|---|
| A | Wallet file + partial password | High | btcrecover password mode |
| B | No seed, no wallet file, no device | Zero | None |
| C | 23 of 24 seed words + one address | Very high (minutes) | seedrecover.py |
| D | Seed + partial passphrase fragments | High if fragments exist | btcrecover --bip39 |
| E | Seed + PIN-locked device | Very high | A compatible hardware wallet |
| F | Seed + unknown BIP standard | High | Sparrow script-type scan |
| G | Non-BIP-39 mnemonic | Depends on knowing software | Original wallet software |
| H | Hardware wallet, no seed | Only with the PIN | The device itself; estate planning for prevention |
What to Do After Recovery
Regaining access is not the end. The old wallet lived on hardware and in environments whose security history you do not know. In my view, the correct final step is a sweep to a fresh wallet.
Generate a new 24-word seed on a hardware device. Write the seed on paper or steel. Verify the first receive address on the device screen, not on the host computer. Send the entire balance from the recovered wallet to the new receive address. Confirm it on a block explorer from a separate online device, then wipe every copy of the old wallet file and destroy the old seed material if it was exposed.
After the sweep, your coins sit under a key whose history you know. In my view, that is the point where recovery is finished.
Preventing the Next Loss
Most of the eight scenarios trace to one root cause: a self-custody setup without redundant, separately stored seed backups. The Bitcoin self-custody guide covers the prevention layer in full. My rule of thumb: set it up once, test it with a recovery drill before you deposit real funds, and these scenarios stay hypothetical.
Recovery Services Are Legitimate but Verify Everything
Some recovery services are legitimate. The space also contains scammers. Verify any operator independently. A real service will see your wallet file or seed words, so only hand them over to a firm you have checked, and move the funds to a fresh seed afterwards.
Disclaimer
This article is educational content for Bitcoin holders and heirs managing self-custody. It is not legal or financial advice. Bitcoin recovery is a high-stakes operation. Make three offline backups of any wallet file before any recovery command runs. Never share your seed phrase with anyone you have not vetted. For complex multi-wallet estate scenarios, consult a professional with verifiable credentials.
