CustodyStress
Archive › Browse by dependency and outcome › Legal Authority Required — Blocked
Part of the CustodyStress archive of observed Bitcoin custody incidents
Legal Authority RequiredBlocked

Legal Authority Required — Blocked

Cases where legal authority required dependency produced a blocked outcome.

33 cases in this intersection. 100% of determinate cases resulted in a blocked outcome. The most common recovery path is legal proceedings.

Archive analysis — 33 cases
Outcomes
100% of determinate cases resulted in blocked access — 31 percentage points above the archive-wide average of 69%. Only 0% resulted in recovered access — one of the lower survival rates in the archive.
Custody type
76% of cases involved exchange custody, followed by software wallet at 9%.
Primary stress condition
61% of cases involve vendor lockout. Legal or authority constraint accounts for a further 24%.
Recovery path
Legal Proceedings is the most documented recovery path (10 cases, 30% of subset). Of those with a determinate outcome, 0% resulted in recovered or constrained access.
Documentation
79% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
33% of cases involved large or very large holdings (10+ BTC).
33
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

33 observed cases
Blocked
33 (100%)
Three Arrows Capital Collapse: $10B Fund, $3.5B Frozen Claims, Founder Flight
Institutional custody
Blocked 2022
Three Arrows Capital, founded in 2012 by Zhu Su and Kyle Davies, operated as a cryptocurrency investment fund managing approximately $10 billion in assets throu
Vietnamese Police Officers Charged in $1.6 Million Bitcoin Robbery
Software wallet
Blocked 2020
In May 2020, Le Duc Nguyen, a Bitcoin holder in Ho Chi Minh City, Vietnam, became the victim of a coordinated robbery by police officers. The officers seized ap
Einstein Exchange Vancouver: $16M CAD Claimed Liabilities, Insolvent Collapse 2019
Exchange custody
Blocked 2019
Einstein Exchange, a Vancouver-based cryptocurrency platform founded by Michael Ongun Gokturk, marketed itself as Canada's fastest-growing digital currency exch
QuadrigaCX Exchange Collapse (April 2019): Mass Custody Loss
Exchange custody
Blocked 2019
QuadrigaCX, founded in 2013 and one of Canada's largest cryptocurrency exchanges, ceased operations on April 15, 2019, with approximately 115,000 users unable t
BitGrail Exchange Collapse: 17 Million NANO Stolen, 230,000 Users Frozen
Exchange custody
Blocked 2018
BitGrail, an Italian cryptocurrency exchange, announced on February 8, 2018 that approximately 17 million NANO tokens—valued at roughly $170 million at the time
QuadrigaCX Exchange Collapse: C$100,000 Withdrawal Never Processed
Exchange custody
Blocked 2018
Eric Z., a QuadrigaCX customer, deposited C$5,000 into the Canadian cryptocurrency exchange around 2014 and grew his position to approximately C$125,000 through
Xitong Zou: QuadrigaCX Creditor During Exchange Collapse and Fraud
Exchange custody
Blocked 2018
Xitong Zou was a customer of QuadrigaCX, a Canadian cryptocurrency exchange that collapsed in late 2018. Like thousands of other users, Zou had cryptocurrency h
Kleiman Estate v. Craig Wright: Bitcoin Access Blocked by Knowledge Concentration
Unknown custody system
Blocked 2018
David Kleiman, a computer forensics expert in Palm Beach County, Florida, died in April 2013. His brother Ira Kleiman later alleged that David and Craig Steven
Cointed GmbH Exchange Collapse: Austria, 2018 — Customer Funds Disappeared
Exchange custody
Blocked 2018
Cointed GmbH, founded in 2016 in Kufstein, Austria, operated as a regional cryptocurrency powerhouse: a custodial exchange, mining operation, and operator of on
Elvis Cavalic and QuadrigaCX: C$15,000 Withdrawal Lost to Exchange Collapse
Exchange custody
Blocked 2018
Elvis Cavalic of Calgary, Alberta was an active QuadrigaCX customer who had accumulated cryptocurrency holdings through trading on the platform. In October 2018
BTC-e Exchange Seized by U.S. DOJ: 1 Million Users Lose Access (July 2017)
Exchange custody
Blocked 2017
BTC-e, founded in 2011 and headquartered in Russia, operated as an unlicensed money transmitter for six years, processing over $9 billion in cryptocurrency tran
WEX.nz US Citizen Lockout: Recovered Funds Inaccessible Due to Geographic Verification Bar
Exchange custody
Blocked 2017
Following the July 2017 FBI seizure of BTC-e exchange assets, the platform's successor WEX.nz announced recovery of 55% of client Bitcoin holdings, with plans t
Homeland Security Bitcoin Seizure: Unencrypted Seed Phrase Discovered During Search
Software wallet
Blocked 2017
BurtW, a BitcoinTalk forum user, revealed in April 2017 that he had been arrested and that Homeland Security conducted searches of both his home and office. Dur
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
Vircurex Withdrawal Freeze: Timothy Shaw's 12.85 BTC Locked Since 2014
Exchange custody
Blocked 2015
Timothy Shaw, a Colorado resident, executed a trade on Vircurex on March 24, 2014, converting his entire dogecoin balance into 12.85 BTC. That same morning, Vir
MintPal/Moolah Exchange Collapse: 3,700 BTC Inaccessible After Ryan Kennedy's Exit Scam
Exchange custody
Blocked 2015
MintPal was a prominent altcoin exchange serving tens of thousands of users in 2014. Following a July 2014 hack that cost approximately $2 million in VeriCoin,
Otohs: 76 BTC Withdrawal Request Refused by Insolvent Cryptsy (October 2015)
Exchange custody
Blocked 2015
On October 5, 2015, a Reddit user identified as Otohs submitted a withdrawal request for 76 BTC from his verified Cryptsy account, which carried no withdrawal l
ThrillHou v. Cryptsy: Account Lockout, KYC Data Misuse, and Alleged Identity Compromise
Exchange custody
Blocked 2015
ThrillHou, a Cryptsy user, experienced repeated account lockouts beginning in 2015. When support staff operating under aliases BigJohn and John McPherson repeat
Vircurex Exchange Freezes Customer Bitcoin Indefinitely After 2013 Hacks
Exchange custody
Blocked 2014
Vircurex, an altcoin exchange operating during the early cryptocurrency era, halted all withdrawals in March 2014 after suffering two significant security breac
MtGox Withdrawal Halt and Bankruptcy: 400K Inheritance Permanently Blocked
Exchange custody
Blocked 2014
In 2014, the largest Bitcoin exchange at that time, MtGox, ceased Bitcoin withdrawals and subsequently filed for bankruptcy protection. A documented case emerge
Mt. Gox Exchange Collapse: Operator Theft and 650,000 Lost Customer Bitcoin
Exchange custody
Blocked 2014
Mt. Gox operated as the dominant Bitcoin-to-fiat exchange from 2010 to 2014, handling approximately 70% of global Bitcoin trading volume at its peak. The platfo
James Howell's Hard Drive: 8,000 Bitcoin Lost in Welsh Landfill
Hardware wallet (single key)
Blocked 2014
James Howell, a British-based individual, accidentally discarded a hard drive containing private keys to approximately 8,000 Bitcoin while cleaning his office a
James Howell's 8,000 Bitcoin Hard Drive: Landfill Loss Without Backup
Software wallet
Blocked 2013
James Howell, a computer professional based in Wales, accumulated approximately 8,000 Bitcoin during the early mining era through a combination of mining and ac
Cryptsy Exchange Collapse: Concealed Hack Left Users Holding Worthless Balances
Exchange custody
Blocked 2013
Cryptsy emerged as the dominant altcoin exchange during the 2013 cryptocurrency boom, facilitating trading in Litecoin, Dogecoin, Feathercoin, and hundreds of a
CoinLab vs. Mt. Gox: Partnership Collapse Traps North American Customer Bitcoin in Legal Limbo (May 2013)
Exchange custody
Blocked 2013
In 2012, Mt. Gox and CoinLab signed a partnership agreement under which CoinLab would assume management of Mt. Gox's US and Canadian customer operations, includ
← PreviousNext →
Browse by dependency and outcome
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