Partial Seed Backup + Missing Passphrase Flag: BTCRecover Recovery Success
SurvivedWallet passphrase was unavailable — a recovery path existed and access was restored.
gab0miner created an Electrum wallet offline using a Linux Live CD on an unspecified date, recording only 11 of the required 12 BIP39 seed words into KeePass along with a custom passphrase ('MyOwnWord'). The user retained comprehensive technical documentation of the wallet creation process, including notes on offline transaction signing with Electrum 4.0.9, and possessed the wallet's zpub (extended public key), permitting balance verification but not fund spending.
On November 22, 2025, gab0miner posted to BitcoinTalk's Electrum subforum describing their incomplete seed backup and requesting technical assistance. They had begun using BTCRecover, a specialized seed phrase recovery tool, but encountered a critical configuration limitation: the tool did not support injecting a known passphrase during brute-force attempts to identify the missing 12th word. Community member noorman0 identified the solution, referencing GitHub issue #582 and recommending the addition of the `--passphrase` code flag before the `--no-eta` parameter in the seedrecover.py file.
After implementing this modification, gab0miner successfully recovered the missing word ('HORROR', positioned mid-sequence) within hours at 5:04 PM UTC on November 22, 2025. The brute-force process completed rapidly despite searching through all 2,048 BIP39 word possibilities, as even legacy hardware handles this computational load efficiently. Following recovery, community member PX-Z requested verification by reimporting the complete 12-word seed plus passphrase and confirming address derivation—reportedly the first public documentation of successful recovery using this specific tool method. The case illustrates a self-custody scenario where incomplete seed backup documentation created temporary access loss, mitigated through technical recovery tools, community troubleshooting, and documentation of a previously undocumented tool capability.
| Stress condition | Passphrase unavailable |
| Custody system | Software wallet |
| Outcome | Survived |
| Documentation | Present but ambiguous |
| Year observed | 2025 |
Why passphrases fail years after they are set
The failure mode documented consistently across observed cases is temporal: the passphrase is set with confidence, not used for an extended period, and then cannot be reproduced exactly when needed. A single character difference — different capitalization, an added space, a slightly different special character — produces a different wallet with a zero balance. The holder may be certain they remember the passphrase while being unable to produce the exact string that was originally set.
What makes this particularly difficult is that there is no signal at the moment of failure. A wrong passphrase does not produce an error message. It opens an empty wallet. The holder sees a zero balance and typically concludes the passphrase was wrong — but without knowing which part was wrong, or by how much.
Professional passphrase recovery services can attempt permutations when the holder has partial information: they remember the general structure, typical patterns they use for passwords, the approximate length, or that it included a specific word. Recovery from total non-recollection is not feasible.
The preventive action is to store a passphrase record — not with the seed phrase, which would defeat its security purpose, but in a separate secure location accessible to the holder and potentially a designated recovery person. A passphrase that exists only in memory has a time horizon: it will eventually be forgotten, and the timing is unpredictable.
Translate