,

BTCRecover Taproot Seed Recovery: Ordinals & Bitget

Over the Christmas New Year break, I got around to adding Taproot support to BTCRecover. That matters because a lot of people are now using Bitcoin wallets that use Taproot addresses, including standard hardware and software wallets, plus some of the newer Ordinals and inscription-focused wallets.

In this article, I’ll walk through how to use BTCRecover with Taproot Bitcoin wallets, and how to handle some of the more common problems I see in real recovery cases: one missing word, two missing words, swapped words, and a 12-word seed that has a valid checksum but still points to an empty wallet.

Watch the video

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

These examples assume you already have a working installation of BTCRecover on your chosen platform. If you do not, install it first and then come back here.

A few important notes:

  • You will be entering seed words into a computer.
  • Treat that computer as sensitive.
  • The safest approach is an offline or amnesic Linux environment.
  • After recovery, move funds to a fresh seed before reconnecting to the internet if possible.

BTCRecover’s Taproot support works with the rest of the tool. Things like passphrases, SLIP39 where applicable, address databases, and GPU acceleration still work as expected. The main extra step is that some non-standard wallets may need custom derivation paths or a command-line flag to force Taproot checking.

Standard Taproot recovery with one missing word

This first example covers standard BIP39/44 Bitcoin wallets that follow the usual rules well. That includes many hardware wallets such as Ledger and Trezor, software wallets such as Sparrow, and also Unisat if you are using it in a standard way.

In this demo, the wallet is missing one seed word. We do not need to change any configuration files. We can run BTCRecover normally.

Steps for a standard Taproot wallet with one missing word

  1. Open your BTCRecover folder.
  2. Run seedrecover.py.
  3. If prompted for a wallet file, choose Cancel if you do not have one.
  4. Select the Bitcoin standard BIP39/44 option.
  5. When asked for an extended public key, enter it if you have one. Otherwise choose Cancel.
  6. Enter the known address associated with the wallet.
  7. Set the address generation limit. The default of 10 is usually fine.
  8. Enter your best guess for the mnemonic, leaving out or marking the missing word according to BTCRecover’s workflow.
BTCRecover GUI asking for an extended public key
BTCRecover asks whether you have an xpub/ypub/zpub; if not, cancel and search by address.
Address limit dialog in BTCRecover
The address generation limit can be left at the default of 10 for most standard wallet recoveries.

One useful detail: many Ordinals and inscription wallets do not generate a long list of new Bitcoin addresses. They often reuse the same address repeatedly. In those cases, an address generation limit of 1 may sometimes be enough. But if you are unsure, keep it at 10. It is a reasonable default.

When BTCRecover finishes, it will show the recovered seed and the derivation path that matched. In this example, the missing word was found quickly because only one position needed to be tested.

BTCRecover finds the seed using a Taproot path
BTCRecover reports SEED FOUND with the matching Taproot derivation path.

After recovery, import the recovered seed into your wallet and confirm that the expected address and balance appear.

What if two words are missing?

If you have two missing words, BTCRecover can still handle it. The process is similar, but the search space gets much larger. Depending on where the missing words are, how constrained the problem is, and your hardware, it may take several hours to run.

Do not panic if the first pass does not finish quickly. A longer run is normal when multiple positions are unknown. Just make sure you have a good best-guess seed and that BTCRecover is running in a safe environment.

Ordinals Wallet: recovering a swapped-word seed

The second example uses a seed generated by Ordinals Wallet. This wallet does not follow the usual Taproot derivation path as cleanly as standard wallets do. Because of that, you may need to edit BTCRecover’s derivation path list before running the search.

In this case, the seed was invalid because two words had been swapped. That is a very common mistake. People write down 12 or 24 words from memory, and two nearby words get reversed without them realizing it.

Steps for Ordinals Wallet with a non-standard Taproot path

  1. Open the BTCRecover folder.
  2. Open the derivationpath-lists folder.
  3. Open BTC.txt in a text editor such as Notepad.
  4. Find the line related to Ordinals Wallet’s non-standard Taproot derivation path.
  5. Uncomment that line by removing the comment marker, usually a hash symbol.
  6. Optionally, if you are confident the address came from Ordinals Wallet, comment out other standard paths to narrow the search.
  7. Save the file.
BTCRecover derivationpath-lists folder
Open the derivationpath-lists folder inside the BTCRecover directory.
BTC.txt showing derivation path options
Edit BTC.txt to enable the correct Taproot derivation path for the wallet you are recovering.

The default BTC.txt file is intentionally broad. It checks many common standard paths. That is useful when you do not know exactly which wallet created the seed. But if you know the wallet, narrowing the list can make the search faster.

After editing the file:

  1. Run seedrecover.py again.
  2. Select Bitcoin standard BIP39/44.
  3. Cancel the extended public key prompt if you do not have one.
  4. Enter the known address from the Ordinals Wallet.
  5. Keep the address limit at 10, or lower it if you are confident the wallet reuses a single address.
  6. Enter your best-guess mnemonic.
Running BTCRecover for the Ordinals Wallet example
BTCRecover starts its search after the derivation path list has been adjusted.

In this example, the recovered seed differed from the original only because two words had been swapped. Once imported into the wallet, the correct balance appeared.

Recovered Ordinals Wallet seed accepted by the wallet
The corrected seed is accepted and the expected Bitcoin balance is visible.

If you have deliberately swapped multiple pairs of words, or if your seed is fully scrambled, you may need to combine this with other BTCRecover techniques such as token lists. The core idea is the same: give BTCRecover a constrained search space and let it test likely corrections.

Bitget: valid checksum but wrong seed

The third example uses Bitget Wallet. This one is especially interesting because the 12-word seed had a valid BIP39 checksum, but it still pointed to an empty wallet.

That can be confusing. If your seed has a valid checksum, you might assume it must be correct. It is not. A valid checksum only means the word list passes the basic mathematical check used by BIP39. It does not prove that every word is the one you originally intended.

In this case, there was a typo in one of the words. The wallet accepted the seed and created an account, but the account had no funds.

Why this happens

A 12-word mnemonic includes checksum bits built into the final word or words. If you replace one word with another that still produces a valid checksum, the wallet may import it successfully. But the derived keys will be different from your original wallet.

So if you see:

  • Wallet imports fine.
  • Address looks normal.
  • Balance is zero.
  • You are sure funds were there before.

Then the seed itself may still be wrong, even though the checksum is valid.

Steps for Bitget with a valid-checksum typo

  1. Restore or import the suspect seed into Bitget Wallet and confirm that it shows an empty balance.
  2. Return to your BTCRecover folder.
  3. Open derivationpath-lists again.
  4. Undo any changes you made for Ordinals Wallet if needed.
  5. Make sure the relevant standard Bitcoin paths are enabled.
  6. Comment out wallet-specific lines that are not needed, including the Ordinals Wallet line from the previous example.
Bitget import screen
Importing a seed into Bitget can succeed even when the seed is slightly wrong.

For this example, we need to run BTCRecover with an extra command-line argument: --force-p2tr. That tells BTCRecover to check derivation paths as Taproot address types. This is useful for wallets like Bitget where you may not know exactly which path was used.

On Windows 11, you can often right-click in the folder and open a terminal there. In PowerShell, the command will look similar to:

python .\seedrecover.py --force-p2tr

The .\ part is just how PowerShell refers to files in the current directory. The important part is the flag:

--force-p2tr
PowerShell ready inside the BTCRecover folder
Open a terminal directly inside the BTCRecover folder before running the command.
Running seedrecover.py with --force-p2tr
The –force-p2tr flag tells BTCRecover to check paths as Taproot address types.

After launching it:

  1. Accept or dismiss the standard security warning.
  2. Select Bitcoin standard BIP39/44.
  3. Cancel the extended public key prompt if you do not have one.
  4. Enter the address where you expected to see funds.
  5. Keep the address generation limit at 10 unless you have a reason to change it.
  6. Enter the best-guess 12-word seed that imported successfully but showed zero balance.
BTCRecover confirms the initial guess has a valid checksum
A valid checksum does not guarantee the seed is correct.

In this example, BTCRecover found the matching seed and reported it against a legacy derivation path even though we had supplied a Taproot address. That can happen when the tool identifies the underlying seed through related key material or path relationships. The important result is that the corrected seed was recovered.

BTCRecover finds the corrected Bitget seed
The matching seed is found after checking with –force-p2tr.

After recovery, import the corrected 12-word seed into Bitget Wallet again. The wallet may take a moment to import. Once complete, the expected Bitcoin balance should appear.

Bitget shows the recovered balance
Importing the corrected seed reveals the funds that were missing before.

Security notes for running BTCRecover safely

BTCRecover is powerful because it can test many possible seeds quickly. But that also means you are entering sensitive recovery data into a computer. Be careful.

Use one of these approaches:

  • Run BTCRecover in an amnesic Linux environment, so the system does not retain data after shutdown.
  • If using a normal desktop, keep it offline while running the tool.
  • Only reconnect to the internet after you have moved funds from the recovered seed to a fresh seed.
  • Do not reuse the old seed for large balances if you suspect it may have been exposed or mistyped in multiple places.

The safest recovery workflow is:

  1. Recover the seed offline.
  2. Verify the expected address and balance.
  3. Create a new wallet with a fresh seed.
  4. Move funds to the new wallet.
  5. Only then reconnect to the internet if needed for further use.

If you are stuck, leave a question in the comments on the video. I do my best to reply. If you need more hands-on help, such as a private session or trusted recovery support, you can request it here: recovery services and consultations.

Key takeaways

  • BTCRecover now supports standard Taproot Bitcoin wallets using the normal BIP39/44 workflow.
  • One missing word is often quick to recover.
  • Two missing words are possible, but may take hours depending on hardware and constraints.
  • Ordinals Wallet may require editing BTC.txt in the derivationpath-lists folder to enable its non-standard Taproot path.
  • Bitget may require running seedrecover.py --force-p2tr so BTCRecover checks paths as Taproot address types.
  • A 12-word seed can have a valid checksum and still be wrong, resulting in an empty wallet.
  • Swapped words and single-word typos are common real-world recovery cases.
  • Always run BTCRecover safely: offline or amnesic Linux is best, then move funds to a fresh seed after recovery.

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