OK, suppose the mnemonic recovery words are correct and in order (can easily be checked offline with iancoleman, they are most likely BIP39 or Electrum recovery words; I'm not too familiar with mobile wallets, not sure if you used Bluewallet (I assume it's mostly blue colored)).

It should be no big problem to formulate a recipe for character substitution and some trickery around your additional mnemonic passphrase if it's some sort of name as you say.

1|! for i
5 for S
0|O for o
and so on. You probably know best what you might have substituted for what. Elaborate!


A real problem is that you don't know any public address of your wallet. But the obvious question is: how did funds got into your wallet?

I assume we're not talking about an empty wallet. Do you have any details of a coin purchase, withdrawal from an exchange or whereever some coins came into your wallet? Think about it, it could be important.

Knowing an address of the wallet provides some anchor to decide which computed additional mnemonic passphrase candidate is the correct solution. Checking all possible candidates for the additional mnemonic passphrase is possible but depends on how many candidates exist (how feasible is it to check the search space manually for coins in a wallet).

It could also be important to know how much you wallet was used, roughly. This is to estimate how many addresses of the wallet could've been used.


Deciding if your wallet addresses are of Bech32 type, starting with bc1q... for Native Segwit, may depend on the age of the wallet. If you know your wallet is older than Native Segwit addresses this could rule those possibly out.

I've done a spending PIN recovery successfully for someone else who forgot it for his Schildbach Android wallet with btcrecover. This guy had only vague memories of it and his memories turned out to be wrong, so it wasn't clear even how long his PIN was. The constrains were a minimum length of 4 and likely less than 9 digits.

This wasn't very hard, only I didn't want to invest much energy because the wallet's value and my share for cracking it wasn't high. I succeeded which was very satisfying both from the learning experience I gained and a happy user who got the majority of his wallet's coins back from me. (He trusted me to send me his wallet file to crack it. It's quite some time ago and wasn't a case in this forum.)

TL;DR
Your case is difficult and that's why you won't get a spoon-feed-me recipe. So far to my knowledge you failed to confirm that your 12 mnemonic recovery words are either a valid Electrum or BIP39 mnemonic seed. This is an easy check, btw. That's not a big deal, but when you're asked about it to remove a possible variable and you don't reply, I'm certainly less motivated to invest time and brain greese in your case. Don't know how others feel about it, maybe same as me?

You don't seem to know any public address of your wallet or do you? What address types "hold" your coins? Can we assume some standard derivation path?

How do you want to brute-force your mnemonic passphrase extension when you don't have a public address as possible anchor (not even knowing its full derivation path)? Any unique mnemonic passphrase produces an unique wallet! You need some anchor to find and pinpoint your correct mnemonic passphrase.

Your case simply has too many unknown variables and uncertainty.

If you know the correct sequence of mnemonic recovery words, if you know an address of that wallet with its full derivation path and the only unknown is either a short enough mnemonic passphrase that thus can be reasonably brute-forced or the mnemonic passphrase is partially known enough so that the search space isn't overwhelmingly large to fill the unknown gaps, then and only then it's a reasonably "easy" brute-force job to crack the unknown variable.

The more uncertainty and unknown variables you introduce the less easy and feasible it becomes.

If you can't constrain the amount of unknowns it simply becomes almost impossible to crack a problem.

What is happening is that you are not providing enough information to help you, we can only try to deduce based on what we read.

We know you have a 12-word mnemonic seed and a password, which gives us these options:

1- Your seed is the backup of your wallet and the password is for accessing the software (just to decrypt the file generated when entering the seed).

In this case, only the seed is useful because it is not related to the password. According to the software used, some seeds did not follow the standard in the past, using custom word lists and derivation paths.

When opening Electrum and entering your seed, does a checksum message appear? Does the continue button activate or do you have to go to options and choose manually?

2- Your seed is a BIP39 seed with an extended phrase.

This is not a common way to create a wallet as these are parameters you must choose manually; generally, users create a traditional seed. In this case, when a seed has an extended phrase you must know exactly what the phrase is, case-sensitive (phrase, password, number).

To force one of these passwords, you should be able to test each variant of the password individually, generate certain amounts of addresses for all their types or at least legacy and segwit, and since you don't know your address, you must check balances.

I wonder:

Do you know who funded your address and thus try to determine what type of address you are using?

If so, it would help reduce your efforts significantly.

Can you ask the person who wrote the data for you if they remember anything that you don't?

Any clue helps.

Do you have in your possession the device where you created the wallet?

If so, you could recover your wallet.dat and the path would be easier.

To be honest, i only used btcrecover for different use case. Anyway, it seems nobody in this forum could give help you need. So at this point, i only could suggest you to contact creator of btcrecover directly.

You should simply be aware that whatever secrets or partial secrets you feed into Ai via your prompts, is no secret anymore. The company behind the Ai can use it for further training or whatnot else. You cease control of your secrets or partial secrets. If this is fine for you, do what you want.
Whoever uses LLM, some call that Ai, should know their limitations and shouldn't believe everything they spit out. As ABCbits said, don't trust blindly, verify!

If you intend continue using AI/chatbot, at least verify what it says.

Tools made by iancoleman generally is trustworthy. But looking at https://iancoleman.io/ and https://github.com/iancoleman, i did not find any tool for recovery or brute force. So i'm confused what you're trying to achieve here.

I just want to remind that BTCRecover actually support address database (contain list of address with balance) which can be be used if you don't have either address, master public key or wallet file.[/list]

Let's assume your mnemonic recovery words are correct by words and their sequence. You can't brute-force a mnemonic passphrase when you don't know any public address of your wallet.

Any individual mnemonic passphrase will give you an unique wallet. There's no right or wrong like with a password entry. Your only chance to know you got your correct mnemonic passphrase is when you can match a know public address of your wallet. How do you want to identify yours without any other details, especially when you don't have any public address of your wallet?

On the other hand if you've transfered some coins into your "unknown" wallet in the past, well, how did those coins get into your wallet? There need to be some transactions with destination outputs, public addresses as receiving ones. Any chance to have records of those? Who did transfer coins into your wallet? I would assume it was you.


A recovery test situation to check if you're able to use BTCrecover correctly could e.g. be:

• a set of 12 mnemonic recovery words with known sequence, the goal here is not to find their correct sequence because we assume the sequence is known and correct
• in the test situation the test mnemonic passphrase is known, but we pretend we only know it partly with some wiggle room for uncertainty
• a list of parts that may comprise the mnemonic passphrase, their correct sequence may need to be determined yet
• other variable parts, like special characters or numbers that can occur at variable spots in the mnemonic passphrase
• if upper or lowercase letters are not certain this can be addressed to, also common typos
• at least one address of maybe known derivation that belongs to your wallet
• you construct rules how BTCrecover should compose and brute-force the mnemonic passphrase (this can be hard for newbies of BTCrecover or those who don't have a clue how such composition rules have to be expressed correctly to effectively exhaust the sample search space for the mnemnoic passphrase

You now run BTCrecover to brute-force the mnemonic passphrase. Your rules must be complete enough so that the real mnemonic passphrase must be constructed at some point correctly by the rules and BTCrecover has to find the solution with the one known public address of the test wallet.

If this test recovery fails and can't find the (prior known) solution, you don't master the tool and you won't succeed in a real recovery situation where you don't know the solution.

Constructing efficient and most importantly sufficient assembly rules for what is the variable part of a recovery and what needs to be properly brute-forced isn't that easy.

It's quite complicated to explain this but it's easy to show an example.
Check this (my) post for a BTCRecover (seedrecover) example of an "easy mode" of the one asked by the OP,
link: https://bitcointalk.org/index.php?topic=5510362.msg64571995#msg64571995

If you need assistance on it, reply with the best description of the situation like the OP in that thread did.

For your mnemonic recovery words (what you call "seed phrase") what does 99.9% certainty mean? Such mnemonic recovery words contain a checksum, partly represented by the last word, and if the checksum is OK, it's highly likely the sequence of recovery words is OK, too.

So, if you're certain about the sequence of your recovery words and you have at least one address of your wallet, you could in theory brute-force your mnemonic passphrase. About 90% certainty for your mnemonic passphrase isn't too bad, of course it depends upon what clues you have about the uncertain part.

My additional advise:
if you try to crack a problem with BTCRecover, construct a recovery test situation first where you know the solution. Try to find this known solution with your cracking procedure. If you can't find it, you highly unlikely will crack your real problem!

By any chance, do you refer to this page https://btcrecover.readthedocs.io/en/latest/bip39-accounts-and-altcoins/?


No. Wallet software typically generate entropy or words using secure RNG rather than fixed in certain ways.

I don't know what exactly your problem is since you said that you have both a seed and a passcode. Why did you still want to find your lost BTC?

If it's beyond the gap limit and this is the reason why you can't find your lost BTC, then BTCrecover is not the tool you need to use.
You should use other tools like the xPub scanner to look for the right derivation or how deep the target address is. This tool can be used for scanning everything from your master public key and check all used addresses with the right derivation path.

So if you can explain and add more details about this wallet, what exactly is your problem?

Do you mean when you asked on this thread Recovering BTC Funds with only Seed Phrase? If so, it may be because btcrecover usually suggested when someone doesn't have all 12/24 seed phrase where they need to brute force it.


Not true, see https://ninjastic.space/search?content=btcrecover.


Yes, although i'd say it's the correct documentation page.


Yes and yes.


Yes, it's created by 3rdIteration from GitHub.


While btcrecover documentation mention you can specify derivation path, there's no mention whether you can configure btcrecover to try various derivation paths. So i doubt it's best tool for your use case.

It probably means you are using the wrong derivation path.

If you remember one of the addresses you've sent bitcoins from or received coins to, then it will make the searching process a lot easier. Maybe it's in an invoice in one of your emails or something, or in a deposit/withdraw history somewhere.


There's way more than 3 possible derivation paths. But for all intents and purposes, there are only a few standard ones.

If you suspect that you created the wallet on Electurm, you should know that it doesn't create BIP39 wallets by default, but uses it's own paths. "m" (meaning "root" i.e. no derivation done yet) for legacy addresses and "m/0'" for segwit.

Offline (air gapped) means no matter what the software does, it can't leak your seed phrase online. That also means you should never go online again with that computer without wiping the drives. I prefer to use a spare laptop for this, running Linux.

Did you try both electrum seed and BIP39 seed?

What 3 derivations are you referring to? If you mean Legacy (P2PKH), P2SH and PWPKH, then these are address types, not derivation paths.

The derivation paths are perfectly explained here: https://learnmeabitcoin.com/technical/keys/hd-wallets/derivation-paths/.

---

Did you try pressing the key "detect existing accounts"?

You can try with some tools
iancoleman's Mnemonic Code Converter.
The FinderOuter, a bitcoin recovery tool.

Use these tools offline!