CustodyStress
Archive › Browse by documentation and custody type › Partial Documentation — Hardware wallet (single key)
Part of the CustodyStress archive of observed Bitcoin custody incidents
PartialHardware wallet (single key)

Partial Documentation — Hardware wallet (single key)

Cases where partial documentation existed for a hardware wallet. Typically: the device location was known, but the seed phrase, PIN, or passphrase was not adequately documented.

44 cases in this intersection. 86% of determinate cases resulted in a blocked outcome and 14% in access survived. The most common recovery path is no path available.

18
Blocked
0
Constrained
3
Survived
23
Indeterminate

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

44 observed cases
Blocked
18 (41%)
Survived
3 (7%)
Indeterminate
23 (52%)
Tax Conviction Forces $124M Bitcoin Disclosure Order, But Keys Remain Inaccessible
Hardware wallet (single key)
Blocked
Richard Ahlgren III, an early Bitcoin investor, was convicted of tax evasion for underreporting capital gains from cryptocurrency sales. A Texas federal court i
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
Mark Frauenfelder's 7 Bitcoin: Household Cleaner Discards Written Seed Phrase
Hardware wallet (single key)
Survived
Mark Frauenfelder, a US journalist, purchased approximately 7 Bitcoin in early 2016 at roughly $3,000 total investment. As the asset price appreciated significa
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
30 BTC Destroyed in House Fire — Hardware Wallet Loss Without Backup
Hardware wallet (single key)
Blocked
A Reddit forum user posted approximately six years ago that their neighbor had lost a hardware wallet containing 30 BTC in a house fire. The device was physical
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
The Hard Drive in the Landfill: $80 Million in Inaccessible Bitcoin
Hardware wallet (single key)
Blocked
In the early years of Bitcoin adoption, a miner accumulated a substantial holding on a single hard drive. At the time of disposal, the device contained Bitcoin
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;
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
0.7 BTC Permanently Inaccessible After Confusing Coldcard Authentication Words With Seed Backup
Hardware wallet (single key)
Blocked
A Bitcoin holder stored 0.7 BTC on a Coldcard hardware wallet and created what they believed to be a complete paper backup. The backup contained only the device
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
USB Pendrive With Encrypted Private Keys Lost—No Backup, No Recovery
Hardware wallet (single key)
Blocked
A Bitcoin holder had constructed a custody system across four wallets: one Ledger hardware wallet and three hot wallets. For the hot wallets, the holder recorde
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
Father Compromises Trezor Seed Phrase via Phishing Site—Permanent Loss
Hardware wallet (single key)
Blocked
A father received a Trezor hardware wallet from his son as an upgrade from Coinbase exchange custody, where the son had experienced multiple password compromise
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 documentation 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