CustodyStress
Archive › More United States cases › United States — Owner death
Part of the CustodyStress archive of observed Bitcoin custody incidents
United StatesOwner death

United States — Owner death

Cases from the United States where Bitcoin became inaccessible following the death of the original holder. These cases reflect the gap between legal inheritance authority and technical access that characterizes most estate-related custody failures.

Archive analysis — 8 cases
Recovery path
Estate Process is the most documented recovery path (6 cases, 75% of subset).
Structural dependency
88% of cases carry a single-person knowledge dependency tag — the most common structural factor in this subset.
8 observed cases
Blocked
2 (25%)
Survived
2 (25%)
Indeterminate
4 (50%)
Widow Inherits Crypto Apps and Recovery Codes After Husband's Death—PIN Unknown
Software wallet
Indeterminate 2019
In August 2019, a widow posted on Bitcoin Stack Exchange seeking help accessing her deceased husband's cryptocurrency holdings. Her 43-year-old husband, in appa
Colorado Bitcoin Investor Death: Family Discovery and Coinbase Estate Transfer 2017
Exchange custody
Survived 2017
A Colorado-based Bitcoin investor died suddenly in 2017 without informing his family of his cryptocurrency holdings. The family had no initial awareness that he
Colorado Estate: Bitcoin Recovered via Coinbase After Sudden Death (2017)
Exchange custody
Survived 2017
A Colorado resident in his twenties died unexpectedly in 2017, leaving his family to navigate an unanticipated cryptocurrency holding. The discovery came only a
Hal Finney's Bitcoin Estate: ALS, Cryonic Preservation, and Unrevealed Succession
Unknown custody system
Indeterminate 2014
Hal Finney was a foundational figure in Bitcoin's emergence: a PGP cryptographer, early cypherpunk, and recipient of the first Bitcoin transaction sent by Satos
Hal Finney: Pioneer Bitcoin Holder Whose Keys Remain Unverified After Death
Unknown custody system
Indeterminate 2014
Hal Finney, a legendary cryptographer and cypherpunk, received 10 BTC directly from Satoshi Nakamoto in January 2009—the first peer-to-peer Bitcoin transaction
Matthew Moody: Early Bitcoin Miner Dies in Plane Crash, Estate Inaccessible
Exchange custody
Blocked 2013
Matthew Philip Moody, 26, of San Ramon, California, was an early Bitcoin miner who accumulated coins during the network's early years using his home computer. O
Dave Kleiman Estate vs. Craig Wright: 1.1 Million Bitcoin, Ownership Unresolved
Unknown custody system
Blocked 2013
Dave Kleiman, a computer forensics specialist based in Florida, was an early Bitcoin developer who died on April 26, 2013, after years of declining health follo
Recovering Bitcoin After Owner Death: Paper Wallet and Computer Access
Software wallet
Indeterminate
In December 2013, a user posted to Bitcoin Stack Exchange asking for help recovering Bitcoin belonging to their brother, who had died in April of that year. The
More United States cases
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