Incomplete BIP39 Seed Phrase: 5 Missing Words, No Backup Record
IndeterminateNo documentation described the custody setup — whether anyone recovered access is not known.
In April 2019, a Ledger Nano S user discovered they had recorded only words 1–19 of their 24-word BIP39 seed phrase, with no record of the final five words (positions 20–24). The wallet contained significant holdings in both Bitcoin and Ethereum. The user approached the problem systematically, calculating that recovery would require testing approximately 1.4×10^14 valid combinations, each requiring 2048 iterations of SHA-512-HMAC hashing to validate.
This totaled roughly 2.87×10^17 hash operations. On consumer GPU hardware operating at 1–13 terahashes per second, the search would take 1.65–3.
3 days at an estimated cost of $28,700. On ordinary consumer hardware, the task would require approximately 1,864 years of continuous computation. The user posted to the Bitcoin Forum seeking technical advice on whether SHA-512 ASIC hardware existed or whether GPU-based brute-forcing represented the only viable option. Responses from experienced developers, including respected contributor HCP, were discouraging.
HCP provided detailed analysis showing that even optimized recovery tools like btcrecover would be impractical for five missing words, achieving only approximately 1,000,000 valid seed checks per 7–8 minutes on consumer hardware. The incident exemplifies a critical self-custody failure: incomplete seed phrase documentation combined with knowledge concentration (sole keyholder, no redundant records). The forum thread contains no follow-up indicating whether recovery was attempted or achieved, leaving the ultimate fate of the assets unknown.
| Stress condition | Documentation absent |
| Custody system | Hardware wallet (single key) |
| Outcome | Indeterminate |
| Documentation | Partial |
| Year observed | 2019 |
| Country | unknown |
What the absence of documentation actually removes
What documentation provides is a starting point. Without it, heirs face three unknowns before they face any access problem: does the Bitcoin exist, where is it held, and what is needed to access it. Most of this information cannot be reconstructed after the owner dies or becomes incapacitated. Educated guesses, blockchain searches, and device inventories occasionally locate wallets — but without credentials, finding the wallet does not help.
Cases in this archive where documentation was absent but recovery succeeded typically involved one of two factors: an exchange account where the heir knew the email address and could navigate the account recovery process, or a designated person who had been given credentials informally and could act. Self-custody without any documentation or designated knowledge-holder is consistently the worst combination.
The content of documentation matters as much as its existence. A note that says "my Bitcoin is in a hardware wallet in the safe" is better than nothing but insufficient. Effective documentation specifies: what type of wallet, where the seed phrase is stored, whether a passphrase exists and where it is documented, and any exchange accounts and the email addresses used. It should be tested — the executor should be able to confirm the information is accurate before it is needed.
Documentation does not need to expose credentials to be useful. A document that describes the custody structure, points to where credentials are stored, and names a person who has been briefed can be stored without security risk. The goal is not to put the seed phrase in a filing cabinet — it is to ensure the executor has a map, not a blank wall.
Translate