CustodyStress
Archive › Browse by outcome and custody type › Indeterminate — Hardware wallet (single key)
Part of the CustodyStress archive of observed Bitcoin custody incidents
IndeterminateHardware wallet (single key)

Indeterminate — Hardware wallet (single key)

Cases where a hardware wallet access failure has an unknown or unresolved outcome. These cases document the structural failure but lack documentation of whether recovery was eventually achieved.

Archive analysis — 25 cases
Documentation coverage
100% of cases have indeterminate outcomes — higher than the archive average of 43%.
Primary stress condition
48% of cases involve seed phrase unavailable. Passphrase unavailable accounts for a further 16%.
Recovery path
Password Bruteforce is the most documented recovery path (5 cases, 20% of subset).
Documentation
92% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
92% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
25 observed cases
Indeterminate
25 (100%)
Ledger Nano S with Incomplete 9-Word Seed Screenshot—$10K Inaccessible
Hardware wallet (single key)
Indeterminate 2024
In March 2024, a BitcoinTalk forum user (Ausnoobi) posted on behalf of their partner seeking recovery assistance for a Ledger Nano S hardware wallet purchased a
Ledger Nano S Hardware Wallet: Incomplete 9-Word Seed Phrase Recovery Failure
Hardware wallet (single key)
Indeterminate 2024
In March 2024, a BitcoinTalk forum user reported a custody access failure affecting approximately USD 10,000 in cryptocurrency held on a Ledger Nano S hardware
Ledger Nano S with Incomplete 9-Word Recovery Phrase: $10K Trapped
Hardware wallet (single key)
Indeterminate 2024
In March 2024, a BitcoinTalk user reported that their partner had lost access to a Ledger Nano S purchased approximately seven years earlier. During initial set
Fragmented BIP39 Seed Recovery: $25M Ethereum Wallet with 6 Missing Words
Hardware wallet (single key)
Indeterminate 2024
In November 2024, a Bitcoin Forum user identified as 'yzeb' disclosed a self-inflicted custody access failure involving an Ethereum HD wallet derived from a BIP
Ledger Nano S Seed Phrase Incomplete: 9 Words of 12 Retained, $10K Inaccessible
Hardware wallet (single key)
Indeterminate 2024
A cryptocurrency holder set up a Ledger Nano S hardware wallet approximately 7 years prior to March 2024, using an older computer at a previous residence. Durin
Ledger Nano S with Incomplete 9-Word Seed Backup: $10K Asset Access Blocked
Hardware wallet (single key)
Indeterminate 2024
In March 2024, a user reported on BitcoinTalk that their partner's Ledger Nano S hardware wallet, purchased around 2017 and set up on an old computer at a previ
Lost Ledger Nano Hardware Wallet: Recovery Blocked by Unknown Derivation Path
Hardware wallet (single key)
Indeterminate 2021
In June 2021, a BitcoinTalk user identified as so98nn reported losing their Ledger Nano hardware wallet while retaining both the seed phrase and passphrase need
Mark Geor's $4 Million Cryptocurrency Safe Stolen in New Zealand Burglary
Hardware wallet (single key)
Indeterminate 2021
In September 2021, thieves targeted the home of Mark Geor in Westmere, New Zealand. The attackers forcibly removed a safe from the property that contained appro
Vincent Everts: Armed Home Invasion During Livestream in Amsterdam
Hardware wallet (single key)
Indeterminate 2021
In December 2021, Vincent Everts, a well-known Dutch technology commentator and trend analyst, was conducting a livestream from his Amsterdam home when armed ho
Missing 2 of 12 Mnemonic Words: Brute Force Recovery Feasibility
Hardware wallet (single key)
Indeterminate 2020
In March 2020, a Bitcoin holder wrote their 12-word BIP39 mnemonic on paper. During storage or handling, the last two words were torn away and lost, leaving onl
1 BTC Locked in Nano Ledger X with Illegible Handwritten Seed Phrase
Hardware wallet (single key)
Indeterminate 2020
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
Illegible Seed Phrase on Nano Ledger X: 1 BTC Recovery via Brute-Force Search
Hardware wallet (single key)
Indeterminate 2020
In January 2020, a BitcoinTalk forum user posted on behalf of a friend who had purchased a Nano Ledger X hardware wallet one to two years earlier. The friend ha
Illegible Seed Phrase Backup: 1+ BTC Inaccessible on Ledger Nano X
Hardware wallet (single key)
Indeterminate 2020
A Ledger Nano X hardware wallet purchased around 2018–2019 held over 1 BTC in a native Segwit address (bc1qyw9dcldzl6jaam0rdz5). The owner had followed standard
Incomplete BIP39 Seed Phrase: 5 Missing Words, No Backup Record
Hardware wallet (single key)
Indeterminate 2019
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 (pos
Ledger Nano S Seed Phrase Transcription Error: Duplicate Words at Positions 9 and 12
Hardware wallet (single key)
Indeterminate 2018
In September 2018, a BitcoinTalk user identified as efreeet reported a custody access failure on a Ledger Nano S hardware wallet. The user had originally genera
Lost Final Word of Ledger Nano S 24-Word Seed: 110,000 Dogecoin Case
Hardware wallet (single key)
Indeterminate 2018
On March 8, 2018, a BitcoinTalk forum user identified as Ma1k reported losing the 24th word of a Ledger Nano S BIP39 recovery seed phrase. The loss occurred aft
Ledger Nano S Application Loss With Missing Seed Phrase Backup
Hardware wallet (single key)
Indeterminate 2018
On May 9, 2018, a BitcoinTalk Hardware Wallets forum user (bPatrick401) disclosed a custody access failure involving a Ledger Nano S device. The incident began
Armory Cold Wallet Restoration Created Unencrypted Wallet With Plaintext Private Keys
Hardware wallet (single key)
Indeterminate 2017
KillerTank maintained Bitcoin in offline cold storage on an air-gapped Raspberry Pi with an 18-word paper backup consisting of 4 random letters per set. In Dece
Ledger Nano S Lockout: Seed Phrase Transcription Error and Checksum Validation Failure
Hardware wallet (single key)
Indeterminate 2017
In December 2017, a Ledger Nano S user reported being locked out of their device after completing initial setup. During device initialization, the user received
Father Lost Access to 1,500 BTC on Hardware Wallet—Child Attempts Recovery
Hardware wallet (single key)
Indeterminate 2011
A father purchased approximately 1,500 Bitcoin around 2011 and stored them on a hardware wallet. At some point, access to the device was lost—either through for
Widow Blocked From Bitcoin Legacy: No Seed Phrase, No Recovery Path
Hardware wallet (single key)
Indeterminate
A Vancouver woman faced an impasse after her estranged husband died unexpectedly. He had held Bitcoin in a self-custody wallet and established an account titled
Deceased Father's Bitcoin: Seed Phrase Found, But Balance Unaccounted For
Hardware wallet (single key)
Indeterminate
In June, a 20-year-old began settling his deceased father's estate during a period of family financial crisis—his mother was unemployed and significant debt rem
Burgled Ledger, Split Seed Across PS5 and Garden, Ex-Partner Extortion
Hardware wallet (single key)
Indeterminate
In late 2024, a Bitcoin holder implemented what appeared to be a redundant custody strategy: half the seed phrase was concealed inside a PlayStation 5 console;
241 BTC Trezor Custody Loss: Forgotten PIN and Failed Seed Recovery
Hardware wallet (single key)
Indeterminate
A Bitcoin holder transferred 241 BTC to a Trezor hardware wallet in late 2015, securing it with a 9-digit PIN. The user documented the seed phrase and initially
Stefan Thomas and the IronKey Trap: 7,002 Bitcoin, 2 Attempts Left
Hardware wallet (single key)
Indeterminate
Stefan Thomas, a programmer, received 7,002 BTC in 2011 as payment for creating an animated educational video about Bitcoin. He stored the private keys on an Ir
Browse by outcome and custody type
Terms guide
Survived
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
Archive inclusion criteria

This archive documents cases where a legitimate owner, heir, or authorized party encountered barriers accessing or recovering Bitcoin due to a failure in the custody arrangement. The central question for inclusion is: did the custody structure fail a legitimate access or recovery attempt?

A case must satisfy all three of the following to be included:

  1. Legitimate access attempt. The person attempting to access or recover the Bitcoin was the owner, a designated heir, an executor, a legal authority, or another party with a legitimate claim — not a thief, attacker, or unauthorized third party.
  2. Custody structure failure. The failure was caused by a property of the custody arrangement — missing credentials, structural dependencies, documentation gaps, knowledge concentration, legal barriers, or institutional constraints — not market conditions, individual-level fraud or theft, or protocol-level issues. Platform-level failures that block legitimate user access are in scope regardless of their cause.
  3. Documentable outcome or access constraint. The case must have a stated or inferable outcome: access blocked, access constrained, access delayed, or access eventually achieved through a recovery path. Cases with entirely unknown outcomes are included only where the structural failure is documented and the constraint is unambiguous.
  • Owner death or incapacity — Bitcoin held in self-custody that becomes inaccessible to heirs or designated parties because credentials, documentation, or operational knowledge were not transferred
  • Passphrase loss — BIP39 passphrase forgotten or unavailable, blocking access to a funded wallet even where the seed phrase is present
  • Seed phrase or wallet backup unavailable — no independent recovery path existed or the backup was destroyed, lost, or never created
  • Device loss without independent backup — hardware wallet, phone, or computer lost or destroyed with no recovery path outside the device
  • Documentation absent or ambiguous — heirs or executors cannot determine that Bitcoin exists, which wallet holds it, or how to access it
  • Knowledge concentration — only one person knew the procedure, passphrase, or access method; that person is dead, incapacitated, or unreachable
  • Multisig quorum failure — a threshold signature arrangement cannot be completed because signers are unavailable, uncooperative, incapacitated, or have lost their keys
  • Legal authority / access mismatch — a court order, probate ruling, or power of attorney establishes legal entitlement but provides no technical path to access
  • Institutional custody barrier — exchange or platform hacks, insolvency, regulatory seizure, or operational failure that caused a access constraint or failure for legitimate users, whether temporary, prolonged, or permanent. The failure of the custodian to remain available or solvent is itself the in-scope event.
  • Forced relocation or geographic constraint — physical access to a device or location required for recovery is blocked by displacement, border restrictions, or political circumstances
  • Coercion — the holder was compelled under threat to transfer Bitcoin or disclose credentials during an access event
  • Hidden asset discovery — heirs or executors locate a wallet or account but cannot access it due to missing credentials or operational knowledge
  • Market losses, investment losses, yield scheme losses, or Ponzi scheme losses
  • Hacks or theft targeting an individual's personal security (phishing, SIM swap, social engineering, malware) where the custody architecture itself did not fail
  • Unauthorized transfers where the holder's custody system was not the cause of the failure
  • Ordinary transaction mistakes — wrong-address sends, fee errors, mistaken amounts
  • Protocol-level failures — cryptographic vulnerabilities, consensus bugs, firmware integrity failures
  • Deliberate burns or tribute burns
  • Cases where the stated loss is unverifiable and no structural custody failure is described

Cases are drawn from public sources including forum posts, news reporting, court documents, academic research, and direct submissions. Each case is reviewed against the inclusion criteria above before publication. Source material is retained and available on request for documented cases.

The archive is observational and descriptive. It does not attempt to document all Bitcoin custody failures — only those meeting the criteria above with sufficient documentation to describe the structural failure and its outcome.

Original text
Rate this translation
Your feedback will be used to help improve Google Translate