CustodyStress
Archive › Structural dependencies › Executor Identification Required
Part of the CustodyStress archive of observed Bitcoin custody incidents

Executor Identification Required

Observed Bitcoin custody cases associated with executor identification required.

27% of determinate cases in this category resulted in a blocked outcome. The most common recovery path is estate process.

Archive analysis — 14 cases
Outcomes
27% of determinate cases resulted in blocked access — 42 percentage points below the archive-wide average of 69%. 36% resulted in recovered access — above the archive average. 36% resulted in constrained recovery.
Custody type
64% of cases involved exchange custody, followed by software wallet at 14%.
Primary stress condition
64% of cases involve owner death. Vendor lockout accounts for a further 21%.
Recovery path
Estate Process is the most documented recovery path (8 cases, 57% of subset). Of those with a determinate outcome, 67% resulted in recovered or constrained access.
Documentation
43% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Geographic distribution
United States accounts for 36% of cases in this subset (5 of 14).
3
Blocked
4
Constrained
4
Survived
3
Indeterminate

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

14 observed cases
Blocked
3 (21%)
Constrained
4 (29%)
Survived
4 (29%)
Indeterminate
3 (21%)
Widow Successfully Accessed 4 Bitcoin After Brother's Death — Estate Recovery
Unknown custody system
Constrained 2024
A 36-year-old man purchased approximately 4 Bitcoin around 2016, during the early adoption phase. He held the asset for roughly seven years without incident. He
Inherited Bitcoin Recovery After Mother's Death: 10 BTC Sold, Remainder Secured
Software wallet
Survived 2020
A sole heir inherited Bitcoin holdings from their mother, who died the day after Thanksgiving 2020. The heir possessed complete recovery documentation: a 12-wor
Matthew Mellon's $193M XRP Estate: Cold Wallets, No Keys, No Plan
Hardware wallet (single key)
Constrained 2018
Matthew Mellon, a member of the prominent Mellon banking family, became a significant cryptocurrency investor in the mid-2010s. His $2 million investment in XRP
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
Deceased Bitcoin Miner: Funds Locked on Coinbase, Lost on SnapCard Closure
Exchange custody
Blocked 2016
A Bitcoin miner died intestate in 2016, leaving behind mining equipment and active cryptocurrency accounts on Coinbase and SnapCard, a now-defunct wallet servic
Coinbase Bitcoin Inheritance Without Estate Plan or Recovery Instructions
Exchange custody
Indeterminate 2015
A Bitcoin advocate died by suicide in March, leaving approximately $15,000 USD in Bitcoin held on Coinbase. The deceased had not designated a recovery contact,
MtGox Civil Rehabilitation Claims Process: Password Reset Barrier
Exchange custody
Constrained 2014
Following the MtGox collapse, Japan's civil rehabilitation framework opened a formal claims process to distribute recovered assets to affected users. However, 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
Mt. Gox Collapse Overshadows Father's Estate: Unrecover­able Bitcoin Loss
Exchange custody
Blocked 2014
Around 2012, a Reddit user posted in a Mt. Gox horror story thread describing a custody failure layered with family loss. His father had died approximately one
Bitcoinica Receivership: 98,000 BTC Lost Across Three Thefts and MtGox Collapse
Exchange custody
Constrained 2012
Bitcoinica, a Bitcoin margin trading platform incorporated as a New Zealand limited partnership and launched by Zhou Tong in September 2011, suffered a cascade
Executor Locked Out: Blockchain.com Wallet After Probate, Email Account Dead
Exchange custody
Blocked
A man's father passed away, leaving behind login credentials and a Bitcoin address recorded in estate documentation. During the multi-year probate process—compl
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
2 Bitcoin Recovered from Deceased Relative's Coinbase Account After Six Years
Exchange custody
Survived
In early 2024, an inheritor searching a deceased relative's email discovered a Coinbase purchase receipt dated three days before the relative's death in 2018. T
Structural dependencies
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