,

BTCRecover Without Known Addresses: Seed Phrase Recovery

If you have tried to restore a wallet from a seed phrase and found that your mnemonic has an error — or you may have forgotten the BIP39 passphrase — but you do not know any of the receiving or sending addresses, you are not out of options. In this guide, I will show you how to use BTCRecover with what is called an AddressDB, so you can test candidate seeds against every address that has ever been used on a supported blockchain.

Watch the video.

This method is especially useful when your wallet may have held more than one coin, or when you only remember part of the seed. If even one transaction ever touched a supported coin — Bitcoin, Bitcoin Cash, Litecoin, Vertcoin, or Monacoin — then that blockchain can be used to help recover access to the full BIP39 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.

Why an AddressDB helps

In my earlier BTCRecover videos, I usually assumed you knew at least one address tied to the wallet you were trying to recover. That is a common situation: perhaps you received funds once and still have that address from an exchange email, a transaction history export, or an old wallet file.

But sometimes you do not know any addresses. Maybe the wallet was used only for sending, maybe the receiving addresses were generated on a device you no longer have, or maybe you simply cannot remember which address to use.

An AddressDB solves that problem by giving BTCRecover a much larger set of “possible matches” to check against. Instead of asking:

Does this candidate seed produce one specific known address?

it asks:

Does this candidate seed produce any address that has ever been used on the blockchain?

The reason this can work is that the address space for these coins is enormous. If you have most of your mnemonic words correct — for example, 22 out of 24 words — and you are testing likely replacements, it is very possible to find a candidate seed that produces an address that has already been used on-chain. That does not prove ownership by itself in every real-world context, but for recovery purposes it is often a strong signal that you have found the correct seed.

This also means that if your BIP39 wallet held several supported coins, you only need one of those coins to have had at least one transaction on its blockchain. You do not need to know the address for Bitcoin specifically if your Vertcoin history exists and can be searched.

Use the correct BTCRecover fork

This method works with my improved fork of BTCRecover. If you are using one of the older repositories I referenced in previous videos, or an unrelated fork, this AddressDB workflow may not work as described here.

The important point is to use the version that supports the address-database recovery method for the blockchains listed in its documentation. The supported coins covered in this guide are:

  • Bitcoin
  • Bitcoin Cash
  • Litecoin
  • Vertcoin
  • Monacoin
BTCRecover fork repository page
Use the BTCRecover fork that supports AddressDB recovery

If you run into issues downloading or building the source, check the project documentation for release packages. I have also packaged a release that includes the source code to make this easier.

Supported blockchains in the BTCRecover docs
Check which blockchains are supported by AddressDB recovery

Pre-made AddressDB files

You do not always need to build an address database from scratch. I have made pre-made AddressDB files available for:

  • Bitcoin
  • Bitcoin Cash
  • Litecoin
  • Vertcoin
  • Monacoin

These can be downloaded, unzipped, and used directly with the supported BTCRecover fork. This is often the easiest path if you already know which coin’s blockchain to search.

The pre-made databases are updated periodically. In this video I mention updating them roughly every six months or so, so check the project documentation for the current files and any notes about date ranges or database size options.

Pre-made AddressDB files section in BTCRecover docs
Pre-made address databases are available from the project documentation

Download a full node client

If you want to create your own AddressDB, you need a full node client for the blockchain you want to parse. A light wallet will not work for this because it does not download the entire blockchain locally.

For example:

  • Bitcoin uses Bitcoin Core
  • Bitcoin Cash can use Bitcoin ABC
  • Litecoin uses Litecoin Core
  • Vertcoin uses its full node client
  • Monacoin has a full node client as well

The key requirement is that the wallet downloads and stores the full blockchain locally. You need access to the raw chain data so BTCRecover’s address-database creation script can scan it.

Vertcoin download page
Download the full node client for the coin you want to search

Sync the blockchain before creating the AddressDB

Once you have downloaded the full node client, run it and let it sync. This is where patience matters.

For Bitcoin especially, make sure you have plenty of free disk space. The transcript notes that the Bitcoin blockchain is massive and can require at least 300 GB of free space in the location where the wallet stores its data. Other coins will be smaller, but you still want enough room for a full sync plus any temporary files your system may need.

When you first run a full node, it will usually ask where to store the blockchain. Choose a drive with enough space and good performance if possible. After starting the sync, wait until the node is fully synchronized before trying to build the AddressDB.

In practice, this can take hours or longer depending on your hardware, internet connection, and which coin you are syncing. For Bitcoin, do not expect this to be quick.

Create an AddressDB from the full blockchain

Once the full node has finished syncing, open a command prompt or terminal and navigate to the folder where you extracted BTCRecover.

The script used in this workflow is create-address-db.py. You can run it with help output first to see the available options. Some important options include:

  • --datadir: points to the full node data directory
  • --dblength: controls how much of the blockchain history is included, depending on the coin and database size you want

For altcoins, or if your full node data is not in the default location, you will usually need to specify --datadir. For example, if Vertcoin data is stored at d:\vertcoin-data, you can point the script there.

create-address-db.py help output
The create-address-db.py script has options for datadir and db length

In the video demo, I create a small Vertcoin AddressDB because Vertcoin is a nice small blockchain for a quick example. The command shown uses:

python create-address-db.py --datadir d:\vertcoin-data --dblength 22
Running create-address-db.py for Vertcoin
Example command creating a Vertcoin AddressDB

The script scans the blockchain and builds a database of addresses that have been used. For Vertcoin, this finished in a couple of minutes in the demo and produced a small file. Bitcoin will take much longer because the chain is far larger.

AddressDB creation finishing
BTCRecover finishes saving the address database

Run BTCRecover with the Vertcoin AddressDB

Once you have an AddressDB, using it is straightforward. If you do not provide a known address or xpub, BTCRecover can default to using an available address database. You can also explicitly point it to a specific AddressDB file using the --addressdb option.

The general idea is:

  1. Open a command prompt in your BTCRecover folder.
  2. Run the seed recovery script.
  3. Tell it you do not have a wallet file, if that applies.
  4. Choose the standard BIP39 wallet type.
  5. Provide your best guess of the mnemonic.
  6. Let BTCRecover test candidates against the AddressDB.

Derivation path matters a lot here. In the Vertcoin example, I used a derivation path close to the default first-account path for Vertcoin. If you are recovering a real wallet, think carefully about which derivation paths your wallet may have used. A wrong derivation path can make BTCRecover miss valid results even if the seed is correct.

In the demo, the best-guess mnemonic had only one word replaced with a placeholder. Because it was a single-word error, the result appeared quickly. Real recovery jobs can take much longer depending on how many unknown words you have and how large your search space is.

Use a Bitcoin AddressDB

The same method works with larger chains such as Bitcoin. In the video, I download a pre-made Bitcoin AddressDB file and extract it to a local drive. The example file used is named addresses-BTC.db.

You then add the database path to your BTCRecover command using:

--addressdb d:\addresses-BTC.db
Bitcoin AddressDB archive file
Downloaded Bitcoin address database file

When BTCRecover starts, it loads the AddressDB. For the Bitcoin database in the demo, it loaded hundreds of millions of addresses that have ever been used on Bitcoin.

BTCRecover loading a large Bitcoin AddressDB
Loading a large Bitcoin address database can take time

If the command appears to hang while loading the AddressDB, one possible cause is insufficient memory. Large databases are memory-intensive. If you do not have enough RAM available, the process may seem stuck even though it is still working through loading and indexing data.

After the database loads, BTCRecover can test your candidate seed against the full set of used addresses in that database. In the demo, it found a matching address without any known receiving or sending address being provided beforehand — simply because that address had already been used once on the blockchain.

Performance and BIP39 passphrase recovery

One useful thing to know is that using an AddressDB does not add a huge performance penalty. BTCRecover can check candidate results against hundreds of millions of addresses at roughly the same speed it checks against one known address, with only a small difference in timing.

This makes AddressDB recovery a practical option even when you are unsure about past addresses. If you have any uncertainty — for example, you think you may have used an address but cannot confirm it — searching the blockchain database can be a better fallback than guessing a single address.

The video demonstrates missing or incorrect words in a seed phrase, but the same approach also works for BIP39 passphrase recovery using the same AddressDB method and commands. If you believe your mnemonic is correct but the wallet still does not restore, testing likely passphrases against an AddressDB can help confirm whether a candidate passphrase produces a used address.

Security notes

Because this process involves seed phrases, be careful about where you run it. I do not go into full setup details in this guide, such as installing Python or configuring a secure Linux environment, because that was covered in earlier videos. If you are doing real recovery work with significant funds involved, consider using an isolated machine, keeping your best-guess mnemonic offline as long as possible, and avoiding exposing the final seed to unnecessary network access.

If you need help assessing whether your situation is recoverable, or if you want guidance before running tools on a high-value wallet, see my wallet recovery services and consultations page.

Conclusion

BTCRecover does not require you to know every address associated with a lost wallet. If you have an AddressDB built from the full blockchain — or use one of the pre-made databases for Bitcoin, Bitcoin Cash, Litecoin, Vertcoin, or Monacoin — you can test partially known BIP39 seeds against all addresses that have ever been used on that chain.

The main requirements are:

  • Use the supported BTCRecover fork
  • Have a full node client and synced blockchain if building your own AddressDB
  • Use enough disk space, especially for Bitcoin
  • Be careful with derivation paths
  • Allow time and memory when loading large databases

If you have a seed phrase error or a forgotten BIP39 passphrase and no known addresses, this is one of the most useful recovery methods available.

Questions from viewers

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

How do I configure BTCRecover to use a downloaded AddressDB file?

You have two options. The easiest is to rename the downloaded database file to 'addresses.db' and place it directly in the main BTCRecover folder; then you don't need any extra command-line arguments. Alternatively, you can keep the file anywhere with any name, but you must include the full path to it using the '–addressdb' argument in your command.

Can I recover a seed phrase if I am missing more than three words?

No, this is generally unrecoverable through brute force. If you are missing one or two words, recovery is feasible (taking from minutes to days depending on the word count). However, if you are missing three or more words, the computational power required makes it impossible for most users, often taking years or longer even with significant hardware. You can only reliably recover if you are missing between 1 and 3 words.

Do I need an AddressDB to recover a Bitcoin Core wallet password?

No, you do not need an AddressDB or download the blockchain for this. Recovering a Bitcoin Core wallet password requires only the wallet.dat file itself. The process is similar to recovering a Blockchain.com wallet password, and it benefits significantly from GPU acceleration.

Why does my program stop at the first match instead of continuing to find all matches?

The default behavior is to stop after finding a valid match to save time. If you want to continue searching for other potential matches (for example, when testing a large password list), you need to manually edit the source code. Specifically, you must uncomment the lines that print the found password and private key, and remove the line immediately following them that causes the program to exit.

Does the size of the AddressDB affect the speed of the recovery process?

Not significantly. As long as you have enough RAM to load the AddressDB into memory, there is no real performance penalty for using a larger database. The main bottleneck in the recovery process is the hashing of possible passwords or seeds, not the lookup operation against the address database.

Can I use BTCRecover to recover funds sent to the wrong chain or a custodial exchange?

BTCRecover is a tool for local cryptographic recovery (like finding a lost seed or password); it cannot retrieve funds that have been sent to a custodial service like an exchange. If you sent coins to an exchange or a different chain where you don't control the keys, your only option is to contact their support team. For specific cases like sending BCH to a Segwit Bitcoin address, the funds may be permanently lost due to protocol limitations.

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