,

Basic BTCRecover Word Seed Phrase Recovery

If you have tried to restore your wallet with your seed phrase and got an “invalid mnemonic” error, do not panic yet. In many real recovery cases I see, the problem is a simple transcription mistake: one word is mistyped, two words are swapped, or one word is missing from the backup you wrote down.

For those kinds of problems, BTCRecover can be very useful. It is an open source tool that helps recover BIP39 seed phrases when you already know most of the words but are not sure about one or two of them.

In this article, I will walk through three basic examples: a Bitcoin native Segwit wallet, a VeChain/VET wallet from Exodus using Ethereum-style derivation paths, and a Dogecoin wallet where the known address came from a second account. You can also Watch the video if you want to see the same process on screen.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

First: keep your real seed phrase safe while testing

Before you run BTCRecover with your actual seed phrase, I strongly recommend doing a dry run first. Use a test seed or a clearly fake backup so you can get comfortable with the tool without exposing anything sensitive.

BTCRecover is open source and simple to inspect, but it does not protect your seed from everything else running on your operating system. If you are going to use your real seed phrase, I recommend running BTCRecover offline. Even better, use an amnesic live Linux environment, such as a live Ubuntu USB setup, so nothing persistent is left behind after the session ends.

At minimum:

  1. Disconnect from the internet before entering your real seed phrase.
  2. Run BTCRecover with networking disabled.
  3. Only reconnect to the internet after you have recovered the correct seed and moved funds to a new wallet or new backup.

Do not run this on an always-online computer with your real seed phrase unless you understand that risk.

What BTCRecover is good at

BTCRecover works best when most of your seed phrase is intact. It is useful for cases like:

  • One word is mistyped.
  • Two words are swapped.
  • One word is missing from the written backup.
  • You have a known address that should belong to the wallet, but the current seed does not restore it correctly.

It is not magic. If you lost most of your seed phrase, or if you only remember a small number of words, BTCRecover will usually not be practical. It is a brute-force recovery tool, so the more unknown words you have, the harder and slower the search becomes.

For basic cases with one or two mistakes, though, it can often find the correct seed quickly, especially when you already know an address that belongs to the wallet.

Example 1: recovering a Bitcoin native Segwit wallet

In this example, we are trying to recover a Bitcoin BIP39/BIP44 wallet using a known receiving address. The seed phrase has a typo in it, so it does not restore correctly into the wallet.

The important point is that for many basic Bitcoin recovery cases, you can use BTCRecover with mostly default settings. You do not need to build complicated command-line arguments if your case is simple.

Step 1: get a known address from the wallet

You need at least one address that you believe belongs to the wallet. This could come from an exchange withdrawal record, a past transaction, or another backup note.

In this example, I use Electrum to show where receiving addresses appear in a standard Bitcoin wallet. The Addresses tab lists receiving addresses by account and index.

Electrum Bitcoin wallet showing receiving addresses on the Addresses tab
Receiving addresses are listed in order, such as Address 0 through Address 9.

For this recovery, I use one address from the first account of the wallet. The exact index matters less than having a real address that belongs to the correct wallet and account.

Electrum Bitcoin wallet with one receiving address highlighted for copying
Select or copy the known address you want BTCRecover to check against.

If you do not have a known address, it can still sometimes be possible to use an address database approach, but that is more advanced. For this basic example, we assume you already have one usable address.

Step 2: run BTCRecover with default settings

Assuming you have downloaded and installed BTCRecover, the basic process is simple:

  1. Open the BTCRecover folder.
  2. Run seedrecover.py. On Windows, this may be as simple as double-clicking it if Python is set up correctly. On Linux or macOS, you can run it from a terminal with python3 seedrecover.py.
  3. When asked for a wallet file, choose the option for a standard BIP39/BIP44 Bitcoin wallet because we are doing seed recovery and do not have an existing wallet file.
  4. If asked for an account extended public key, cancel or skip it if you do not have one. Some hardware wallets can provide this value, and it can help narrow the search, but it is not required for this example.
  5. Enter the known address from the first account.
  6. Keep the default address generation limit unless you know your address is deeper in the wallet. The default checks a reasonable range of early addresses.
  7. Paste your best guess of the seed phrase.

For many simple Bitcoin mistakes, that is enough. BTCRecover will test likely corrections and compare the generated addresses against the known address you provided.

Step 3: check the result

When BTCRecover finds a match, it reports the corrected seed and the derivation path where the known address was found.

BTCRecover terminal output showing that a matching seed was found
The terminal shows the recovery result and the derivation path where the known address matched.

In this example, the mistake was very simple: one word in the backup had been written incorrectly. That is exactly the kind of error BTCRecover handles well.

Once you have the corrected seed phrase, verify it carefully before trusting it with funds. Restore it into a clean wallet on an offline or trusted machine, confirm that the known address appears where expected, and then move your funds to a new backup if needed.

Example 2: recovering a VET wallet from Exodus using ETH clone paths

The second example uses BTCRecover’s Ethereum-style wallet functionality to recover a VeChain/VET address from Exodus. The same idea applies to many other Ethereum clones or EVM-compatible chains, such as Binance Smart Chain wallets that use standard Ethereum derivation paths.

For some of these chains, you may need to adjust the derivation path list file so BTCRecover checks the right paths.

Step 1: open the ETH derivation path list

Inside the BTCRecover folder, there is a folder called derivation_path_lists. This contains text files for different coin types and wallet styles.

For Ethereum-style wallets, open the eth.txt file in a plain text editor such as Notepad.

The file contains lines that tell BTCRecover which derivation paths to test. Lines that start with a hash symbol are ignored. By default, the ETH function checks common current and legacy Ethereum derivation paths. That means it can often work for many standard Ethereum wallets without any changes.

For this VET example, we need to enable the VET path and narrow the search by disabling or commenting out the standard Ethereum lines that do not apply.

In practice:

  1. Open eth.txt.
  2. Find the line for VET.
  3. Remove the hash symbol from the start of that line so it becomes active.
  4. Add a hash symbol to the standard Ethereum lines if you know your wallet is definitely VET and not plain ETH.
  5. Save the file.

You do not need to overthink this too much. If you are unsure, leaving extra paths enabled is usually safer than commenting out too many options. The main goal is to make sure the path for your actual coin or chain is active.

Step 2: run BTCRecover as an Ethereum-style wallet

Now run seedrecover.py again using the same basic process:

  1. Choose that you do not have a wallet file.
  2. Select the Ethereum wallet option, which also covers ETH clones depending on what paths are enabled in the edited file.
  3. Skip the extended public key if you do not have one.
  4. Enter the known VET address.
  5. Set an account generation limit. For many Ethereum-style wallets, a lower number can be enough because the receiving address may not change every time you click receive. However, leaving it at a modest default such as 10 is usually fine and reduces the chance of missing something important.
  6. Paste your best guess of the seed phrase.

In this example, BTCRecover found the corrected seed quickly. The mistake was that two words in the backup had been swapped. Again, this is a common human error when copying or writing down a mnemonic.

The result screen can show candidate addresses related to the derivation path being tested. In the VET case, the relevant path uses the VeChain coin type rather than standard Ethereum.

BTCRecover dialog showing candidate VET addresses for selection
Candidate VET addresses are shown under the active VET derivation path.

If your wallet is a Binance Smart Chain wallet that simply uses standard Ethereum derivation paths, you may not need to change anything in the ETH file. In many cases, the default ETH settings will already cover it. But if you are working with a less common EVM chain or a wallet that uses a nonstandard path, editing the relevant derivation path list is often the key step.

Example 3: checking multiple Dogecoin accounts

The third example covers a situation where your known address may not come from account zero. Some wallets allow multiple accounts for the same coin. If you are not sure which account an address belongs to, you need to tell BTCRecover to check more than just the first account.

For this example, I use Dogecoin because it is a common BIP39/BIP44 case and people often have multiple DOGE accounts in wallets that support them.

Step 1: edit the Dogecoin derivation path list

Open the derivation_path_lists folder again and open the Dogecoin file.

By default, BTCRecover usually checks only the first account for a given coin. To check more accounts, you adjust the last number in the derivation path lines. That final number represents the account index.

For example, if you want to check the first three accounts:

  1. Open the Dogecoin derivation path file.
  2. Change the account index values so they include 0, 1, and 2.
  3. Save the file.

This tells BTCRecover to test addresses from those accounts when searching for a match.

Step 2: run the recovery with the known address

Then run seedrecover.py again:

  1. Choose that you do not have a wallet file.
  2. Select Dogecoin as the wallet type.
  3. Skip the extended public key if you do not have one.
  4. Enter the known Dogecoin address.
  5. Keep the address generation limit at a reasonable default, such as 10, unless you know your address is deeper in the account.
  6. Paste your best guess of the seed phrase.

In this example, the search took slightly longer than the first two examples, but it still completed quickly on the test setup. It also moved into a broader phase where BTCRecover allows for one mistake that could be an entirely different word, not just a simple typo.

The result showed that the matching seed was found in the second account, not the first. The backup had a single-word error: one expected word had been replaced by another. That kind of mistake is easy to make when copying a long list of words under stress.

Practical tips for getting better results

If you are new to BTCRecover, start with simple cases. Replicate the examples in this article using test seeds before touching your real backup. You can generate a test seed phrase and intentionally make one or two small mistakes so you understand how the tool reports the result.

A few practical points:

  • Use a known address whenever possible. It greatly improves reliability.
  • Keep your best-guess mnemonic as close to what you actually wrote down as possible. Do not “fix” words unless you are certain they were changed.
  • If you have an account extended public key from a hardware wallet or other source, provide it when available. It can help narrow the search.
  • For Ethereum-style chains, check whether your chain needs a specific derivation path file change.
  • For multi-account wallets, edit the relevant coin file so BTCRecover checks the accounts you need.
  • Do not comment out too many paths unless you are confident about which one applies.

Running BTCRecover through all basic possibilities can take time depending on your hardware and how broad the search is. For simple one-word or two-word mistakes, though, many recoveries finish quickly. In my experience, most practical cases I help with involve only a small number of incorrect words unless someone has scrambled the seed, lost half the backup, or made an unusual mistake.

When BTCRecover will not work

It is important to manage expectations. BTCRecover cannot recover a wallet if you do not have most of the seed phrase. If you lost all of your seed words, there is no practical recovery method available today. Anyone claiming they can magically restore a wallet from nothing is almost certainly a scammer.

If you are missing many words, such as six or more out of twelve or twenty-four, recovery is not realistic at this time. It may become possible much further in the future with far more powerful computing, but that is not something to rely on now. Do not throw away any partial records you have, because even incomplete information can sometimes help if paired with other evidence or future tools.

For simple transcription errors, though, BTCRecover is often the right first tool to try.

Getting help

If you are stuck, free support for these kinds of questions happens in the YouTube comments section on my channel. I do my best to answer questions there when possible.

If you want more structured help, I also offer paid options, including a consultation to walk through BTCRecover setup with demo seeds and a trusted recovery option if you are not confident doing it yourself. The details for those services are available at cryptoguide.tips/recovery-services-consultations.

The main takeaway is this: if your seed phrase has one or two small mistakes and you have a known address, BTCRecover can often recover the correct BIP39 mnemonic quickly. Just work carefully, test first in a safe environment, and keep your real seed phrase as protected as possible until the recovery is complete.

Questions from viewers

Common questions from the comments on this video, with my answers.

Can I use BTCRecover for wallets that don't follow BIP39 standards, like Waves or Helium?

It depends on the specific wallet. For coins like Helium, BTCRecover supports them directly; you just select the wallet type in the GUI (and install `pynacl` if prompted). However, for wallets like Waves, the process of going from mnemonic to address is totally different and incompatible with standard BIP39, so it won't work out of the box. If a coin isn't supported, it can sometimes be added if you sponsor the feature. If you’d like hands-on help, see wallet recovery services.

What should I do if my seed phrase is valid but the wallet app says it's invalid or shows a zero balance?

If BTCRecover finds your seed using an address, then that seed is correct for that specific derivation path. If the wallet app still rejects it or shows no funds, you likely have a typo in the seed (even one that passes checksums, like confusing 'soft' and 'sort'), or you are using the wrong derivation path/account index. Check the exact derivation path BTCRecover matched against. Also, ensure you aren't mixing up hardware wallet seeds with software ones, as some hardware wallets (like Trezor) might accept an incorrect 12-word seed that happens to pass the checksum.

How long does recovery take if I am missing more than two words?

One missing word takes seconds, two takes minutes, three takes days, and four takes years. If you know the position of the missing words, you can use command line arguments to specify placeholders (like 'X') for those spots. Note that if you don't know the position of the missing words, the maximum number of missing words you can realistically recover is two. For larger gaps, such as scrambling 18 words, it is mathematically impossible to recover today.

I'm getting errors about missing modules or files when running BTCRecover on Windows. How do I fix this?

These errors usually mean you are missing dependencies or running the script from the wrong folder. Common fixes include installing specific Python modules mentioned in the error message (such as `py-crypto-hd-wallet` or `groestlecoin_hash`). On Windows, you may also need to install C++ build tools if a module fails to compile. If you see a 'FileNotFoundError' for a pathlist, ensure you downloaded the repository correctly and haven't renamed or deleted the file. You can also try typing `python seedrecover.py` directly in the command prompt instead of double-clicking the file.

Can I recover a seed if I only have the wallet address and no seed words at all?

No. If you have zero seed words and no other wallet data (like a keystore file or backup), the loss is unrecoverable. The address alone is not enough to brute-force the entire seed space. You need most of the seed words (e.g., 9/12 or 10/12) to make a recovery feasible.

Does BTCRecover support Solana or Phantom wallets?

Yes, BTCRecover now supports Solana. You don't need a special file; just select the Solana wallet type in the tool. Keep in mind that Solana doesn't have configurable derivation paths in the same way Ethereum does, so you will rely on the default path or the one selected in your wallet software. If you are having trouble, create a test wallet to verify the process works before applying it to your real funds.

Stuck with a wallet recovery?

I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.

Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides