, , ,

BTCRecover for Segwit Bitcoin Addresses: Seed Recovery

If you have a damaged or partially remembered Bitcoin recovery phrase and you know at least one public address that belonged to the wallet, BTCRecover can help you recover it. In this guide, I’ll show you how to use the Segwit-compatible version of BTCRecover for Bitcoin addresses that start with 3.

This is a follow-up to my earlier BTCRecover guide. The main differences here are simple: you need the Segwit-compatible fork, and you need to use the correct BIP32 derivation path. If your address starts with 1 or bc1, this article may not be the right one for that specific address format.

Watch the video if you want to see the exact commands and workflow on screen.

BTCRecover GitHub repository and Segwit notes panel
The GitHub repository for the Segwit-compatible BTCRecover fork, with a notes panel showing the recovery setup.

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.

What You Need Before Starting

Before you begin, make sure you have these things ready:

  1. Your best-guess 24-word BIP39 seed phrase.
  2. At least one public Bitcoin address that was used by a wallet connected to that seed.
  3. A computer where you can run the tool safely.
  4. The Segwit-compatible BTCRecover fork, not the standard version from my earlier guide.

A very important point: a public address alone is not enough. There is no way to derive a private key from just a public Bitcoin address. If all you have is an address and no recovery phrase or best guess of one, this method will not help you recover your funds.

The reason BTCRecover can work in the right situation is that it tests likely variations of your seed against known derivation paths and checks whether any derived address matches the address you already know. That is why a known public address is so useful: it gives the tool something to verify against.

Why You Need the Segwit-Compatible Fork

The standard BTCRecover workflow from my earlier video does not handle this type of Segwit Bitcoin address correctly by itself. For this example, we need the special Segwit-compatible fork.

In the video, I use a repository that contains the version needed for this kind of recovery. You can download it as a ZIP file and unzip it anywhere on your computer. If you are using Ubuntu or another Linux setup from my earlier guide, you can also unzip it onto a USB stick and run it in the same way.

Downloading the Segwit-compatible BTCRecover fork
The GitHub repository with the Clone with HTTPS option open.

You do not need to understand every part of the code. You just need to use the correct folder and the correct command-line options for the address type you are trying to recover.

Example Setup: Damaged Seed and Known Segwit Address

In my example, I start with a 24-word seed that has two words swapped. That is a very common mistake people make when writing down or remembering a recovery phrase. A small change like that can make the whole wallet inaccessible if you do not know which order was correct.

I also have a known public Bitcoin address from my records. In this case, it is a Segwit-style address because it starts with 3. That tells us we need to use the Segwit-compatible tool and the matching derivation path.

The example uses these paths:

  • Account 0: m/49'/0'/0'
  • Account 1: m/49'/0'/1'

You may not know in advance which account contains the address you remember. That is why it makes sense to test likely accounts quickly before moving on to slower searches.

Running BTCRecover Safely

Security matters a lot here, because if someone gets your 24-word seed, they have access to all of your crypto assets connected to that seed.

For the demo in the video, I run it on Windows because the example seed has no real funds associated with it. But for a real recovery involving significant value, my recommendation is stronger: use an air-gapped Linux setup if you can. That means using a computer or live USB environment that is not connected to the internet while you are working with your seed.

If you must run this on a normal internet-connected Windows machine, treat it as a temporary step. As soon as you recover the phrase, restore it into a safe wallet and move your funds to a new verified seed. Do not leave valuable assets sitting in a wallet whose recovery phrase was typed into an ordinary daily-driver computer.

Quick Recovery vs Slow Recovery

The tool has different commands depending on what kind of error you are trying to fix.

Start with the quick recovery command. It is fast enough that you can run it against several likely derivation paths if you are not sure which account your remembered address belongs to. In my example, the quick search checked a limited number of addresses and finished in a reasonable amount of time.

The slower command is useful when you suspect a bigger error, such as one word being completely different from what should be there. That type of search can take much longer, sometimes days if you are checking many possibilities. If you have a large amount at stake and the quick options fail, it may still be worth running a slower recovery in the background while you continue testing other likely paths.

But for many common mistakes—swapped words, one word slightly wrong, or an address in a later account—the quicker commands are often enough to get you back on track.

Quick and slow BTCRecover command reference
A notes panel listing the quick and slow recovery commands for Segwit accounts.

Step-by-Step Recovery Workflow

Here is the practical workflow I use in the video:

  1. Download the Segwit-compatible BTCRecover fork.
  2. Unzip it on your computer or USB stick.
  3. Open a terminal or command prompt inside the correct folder.
  4. Run the quick recovery command for account 0 first.
  5. Enter the known public address when prompted.
  6. Enter your best-guess seed phrase.
  7. Wait for the tool to finish checking that path.
  8. If it does not find a match, repeat the process for account 1.
  9. If needed, test other likely accounts before moving to slower typo searches.

The important thing is not to jump straight into the longest, most expensive search unless you have reason to believe your error is more complex than a simple swap or path mismatch.

Empty terminal ready to run BTCRecover
A Windows command prompt ready for the BTCRecover recovery command.

Testing Account 0 First

In my example, I first test account 0 using the path m/49'/0'/0'. This is a natural starting point because many wallets begin with account 0.

I paste in the known address and enter my best-guess seed. The tool then runs through the expected derivation process and checks whether any of the derived addresses match the one I provided.

In this particular demo, it does not find the seed on account 0. That is not unusual. Sometimes the address you remember belongs to a later account in the same wallet. If that happens, do not assume the tool failed. Move to the next likely account and try again.

BIP32 path m/49'/0'/0' highlighted for account 0
The notes panel highlights the BIP32 path used for account 0.

Testing Account 1 and Finding the Seed

Next, I run the same type of quick recovery command, but this time against account 1 using m/49'/0'/1'. The only meaningful change in the path is that final number: it changes from 0 to 1.

I enter the same known address and the same best-guess seed. This time, the tool finds a match quickly. It returns the corrected seed phrase, showing that the two swapped words are now in the correct order.

That is exactly why testing multiple accounts can be so useful. The error in the seed may have been simple, but the remembered address may not have been in the first account you tried.

Terminal ready to run the account 1 recovery command
The command prompt and reference notes for running the Segwit recovery command.

What to Do After Recovery

Once BTCRecover returns a seed, verify it carefully before trusting it with real funds.

  1. Copy or write down the recovered phrase exactly as shown.
  2. Restore it into a trusted wallet on a clean device if possible.
  3. Confirm that you can access the expected addresses and balances.
  4. If this was run on an internet-connected machine, move your funds to a new seed.
  5. Test your backup of the new seed before considering yourself safe.

This last step is critical. A recovered phrase is only as good as the security environment it was handled in. If you typed it into a normal Windows PC that may have logging, malware, or other risks, do not assume it remains private forever. Transfer funds to a fresh wallet with a new recovery phrase and verify that backup properly.

Final Thoughts

BTCRecover is a very practical tool for fixing common seed-phrase mistakes, especially when you already know one public address connected to the wallet. For Segwit Bitcoin addresses, the key is using the correct fork and the correct derivation path. Start with quick searches across likely accounts before moving on to slower typo-based recovery options.

If you are dealing with a real loss and feel stuck after trying these steps, I also offer recovery services consultations for people who need guidance on the safest next move.

Questions from viewers

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

How many missing seed words can I realistically recover with BTCRecover?

As a rule of thumb, if you know the positions of the missing words, recovering 3 missing words takes about a day on a mid-range CPU. Recovering 4 missing words will take around 5 years, 5 will take 10,000 years, and 6 will take over 20 million years. If you have a mix of known positions and scrambled words (like 6 known positions plus 6 scrambled), that is a different scenario and can be solved much faster, but standard recovery for more than 3 unknowns is not feasible.

I am getting an 'ImportError: No module named coincurve' when running seedrecover.py. How do I fix this?

You need to install the missing Python library. You can usually fix this by running `pip install coincurve` in your command line or terminal. This dependency is required for the tool to function correctly.

Can I use BTCRecover on a Mac?

Yes, the tools work on Mac. You just need to ensure you have Python 2.7.17 and PIP installed. Once those are set up, the instructions are the same as on other platforms. If you have trouble installing PIP, check the official PIP installation guide for MacOS. (Apps and tools change, so check the current version if something looks different.)

Is there a way to verify if two different Bitcoin addresses come from the same seed phrase?

There is no way to know for sure if any two addresses are derived from the same seed, especially if one might have used a BIP39 passphrase (25th word). The only thing you can do is make an educated guess if both addresses were inputs for a single transaction in the past, which suggests they are from the same wallet. Otherwise, if you still have access to the seed, you can generate the addresses to see if they match, assuming no passphrase was used.

I sent coins to the wrong address or the wrong network (e.g., BCH to Litecoin). Can you help me get them back?

This depends on what exactly happened. If you sent to a standard Bitcoin address starting with '1', it might be recoverable depending on the wallet. However, if you sent to a completely different network like Litecoin, the process is different. I would need to know which wallet software you used and the specific type of address involved to determine if there is a solution. In some cases, you may need to contact the support team of the exchange or wallet provider you used. If you’d like hands-on help, see wallet recovery services.

I forgot my BIP39 passphrase (25th word) but I have my recovery phrase and a known address. What should I do?

If you have the recovery phrase (the 12 or 24 words), that is your BIP39 seed. You should try restoring the wallet using that seed phrase directly. If the wallet asks for a passphrase and you don't remember it, you can try leaving it blank first. If that doesn't work, you can use BTCRecover to attempt to find the missing passphrase, provided you have a known address associated with that seed.

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