1 BTC Locked in Nano Ledger X with Illegible Handwritten Seed Phrase
IndeterminateNo documentation described the custody setup — whether anyone recovered access is not known.
In January 2020, a BitcoinTalk user posted on behalf of a friend who had purchased a Nano Ledger X hardware wallet one to two years earlier and held over 1 BTC in a native Segwit (Bech32 P2WPKH) address. The friend had followed standard practice by writing down the 24-word BIP39 recovery seed phrase, but the handwriting was too poor to be legible or reconstructed with confidence. The friend retained knowledge of the wallet's public address (bc1qyw9dcldzl6jaam0rdz5...) showing a confirmed balance over 1 BTC, but could not read the original seed.
The original poster attempted a brute-force workaround: generating approximately 1,000 candidate mnemonics that each passed BIP39 checksum validation, then testing them against the known address using Electrum's native Segwit derivation path to check for a balance match. This approach proved impractical at scale and risked address reuse if tested without isolation. Community members offered technical guidance. The most practical suggestion came from Pmalek, who identified that if the Ledger device itself remained available, the friend could bypass seed recovery entirely: (1) transfer all funds from the old device to a temporary address, (2) reset the Ledger to factory settings to generate a new seed, (3) write down the new seed clearly, and (4) transfer funds back.
This path required the hardware device but eliminated seed-guessing. The thread did not disclose whether the device was still in the friend's possession, whether any recovery method was attempted, or whether the funds were ultimately accessed. The case exemplifies knowledge concentration and inadequate physical documentation—the seed existed but was rendered useless by poor transcription, while the hardware device's status remained unknown.
| Stress condition | Documentation absent |
| Custody system | Hardware wallet (single key) |
| Outcome | Indeterminate |
| Documentation | Partial |
| Year observed | 2020 |
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