CustodyStress
Archive › Browse by dependency and custody › Passphrase Dependency — Hardware wallet (single key)
Part of the CustodyStress archive of observed Bitcoin custody incidents
Passphrase DependencyHardware wallet (single key)

Passphrase Dependency — Hardware wallet (single key)

Cases where a hardware wallet required a BIP39 passphrase that was not documented independently. Without the passphrase, the seed phrase alone cannot restore access.

50% of all Hardware wallet (single key) cases in the archive involve this structural dependency. The blocked rate among them is 73% — 4 points above the archive-wide blocked rate of 69%. The most common recovery path is coerced transfer.

16
Blocked
0
Constrained
6
Survived
13
Indeterminate

73% of determinate cases resulted in blocked or constrained access.

35 observed cases
Blocked
16 (46%)
Survived
6 (17%)
Indeterminate
13 (37%)
2.3 Bitcoin Inaccessible on Ledger Nano S: Owner Incapacity and Undocumented Credentials
Hardware wallet (single key)
Blocked
In 2019, one partner in a 16-year relationship created a Ledger Nano S hardware wallet and transferred 2.3 Bitcoin to it. The partner deliberately withheld both
When Bitcoin Seed Phrases Are Lost at Death: Community Debate on Permanent Custody Failure
Hardware wallet (single key)
Blocked
A Reddit discussion explored a recurring custody failure scenario: an individual holds Bitcoin in self-custody using only a seed phrase known solely to them, wi
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
Hardware Wallet and Seed Phrase Lost in House Fire
Hardware wallet (single key)
Blocked
A Bitcoin holder experienced a catastrophic loss when a house fire destroyed multiple custody components at once: the hardware wallet itself, the computer used
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
Trezor Hardware Wallet: 0.1 BTC Inaccessible After PIN Loss and Seed Destruction
Hardware wallet (single key)
Blocked
A Trezor hardware wallet user held 0.1 Bitcoin on the device approximately two years after initial purchase. The recovery seed phrase had been written down on p
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
Bitcoin in Cold Storage Lost Permanently Due to Owner Death
Hardware wallet (single key)
Blocked
Forum discussions document a recurring custody failure: individuals who held Bitcoin in self-managed cold storage wallets died without sharing access informatio
South African Investor Tortured and Coerced Into Cryptocurrency Transfer
Hardware wallet (single key)
Blocked
A South African investor holding approximately 100,000 in cryptocurrency in self-custody became the target of a violent attack. The attacker employed torture an
British Columbia Home Invasion: $1.6M Bitcoin Forced Transfer Under Duress
Hardware wallet (single key)
Blocked
In British Columbia, a couple fell victim to a targeted home invasion in which three attackers entered their residence and subjected them to a 13-hour ordeal. D
← PreviousNext →
Browse by dependency and custody
Related pages
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