CustodyStress
Archive › Structural dependencies › Institutional Cooperation Required
Part of the CustodyStress archive of observed Bitcoin custody incidents

Institutional Cooperation Required

Cases where completing recovery required active cooperation from an exchange, custodian, or institution — and that cooperation was unavailable, delayed, or blocked.

Cases where institutional cooperation was required to complete recovery show a 60% blocked rate among determinate cases — and a 5% survival rate. The institution becomes the structural gatekeeper: when cooperation is withheld, delayed, or becomes impossible through insolvency, the recovery path closes entirely.

96
Blocked
57
Constrained
8
Survived
37
Indeterminate

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

198 observed cases
Blocked
96 (48%)
Constrained
57 (29%)
Survived
8 (4%)
Indeterminate
37 (19%)
Mt. Gox SEPA Withdrawal Delayed 28 Days: lukcoin's Unresolved Case (May 2013)
Exchange custody
Indeterminate 2013
On May 7, 2013, BitcoinTalk user lukcoin posted in the Mt. Gox withdrawal delays thread describing a SEPA transfer initiated on April 9 that had not arrived aft
Institutional lockout — Mt. Gox (2013)
Exchange custody
Indeterminate 2013
On April 8, 2013, BitcoinTalk Legendary-ranked user el_rlee submitted a withdrawal request to Mt. Gox. Twelve days later, on April 20, el_rlee posted in a gathe
Mt. Gox Bitcoin Withdrawal Crisis: Weeks-Long Delays Signal Terminal Operational Failure
Exchange custody
Blocked 2013
By November 2013, Mt. Gox customers attempting to withdraw Bitcoin faced indefinite waiting periods, a critical escalation from earlier fiat-only delays. What h
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
Inputs.io Hack: 4,100 BTC Stolen, Partial Refunds October 2013
Exchange custody
Constrained 2013
Inputs.io was an Australian-hosted Bitcoin wallet service operated by a developer known as TradeFortress. On October 23, 2013, the platform suffered a security
Intersango Exchange Collapse: 2000 BTC User Funds Retained by Operator — Norman v. Strateman
Exchange custody
Blocked 2012
Intersango, a UK-based Bitcoin exchange co-founded by Amir Taaki and Patrick Strateman, ceased operations in 2012 after losing its banking relationship. At the
CryptoXChange Exchange Collapse: Users Locked Out of Bitcoin Deposits
Exchange custody
Blocked 2012
CryptoXChange launched on November 10, 2011, as an Australian Bitcoin exchange offering two-factor authentication features including Yubikey support. The platfo
BTCex Unexpected Maintenance Closure and Permanent Platform Shutdown (July 2012)
Exchange custody
Blocked 2012
BTCex operated as a custodial Bitcoin exchange during the early market period. In May 2011, the platform suffered a critical security breach resulting in the lo
BitMarket.eu: Operator Speculation and Bitcoinica Collapse Froze 18,787 BTC in Customer Funds
Exchange custody
Blocked 2012
BitMarket.eu launched in April 2011 as a Polish peer-to-peer Bitcoin exchange. The platform operator, Maciej Trębacz, made a critical decision to invest custome
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
BitFloor Exchange Collapse: 24,000 BTC Theft, Minimal Restitution, Platform Shutdown
Exchange custody
Blocked 2012
BitFloor, a Bitcoin exchange operating in 2012, suffered a catastrophic custody failure on September 4, 2012. An attacker gained access to an unencrypted backup
Bitcoin.de Account Lock: 0.01 BTC Inaccessible Due to KYC Residency Requirements
Exchange custody
Blocked 2012
A Bitcoin user created an account on bitcoin.de, a German peer-to-peer marketplace, during Bitcoin's early adoption period and deposited 0.01002 BTC. The accoun
Tradehill Exchange Shutdown: Users Locked Out After Dwolla Payment Reversal
Exchange custody
Constrained 2012
Tradehill operated as one of Bitcoin's earliest and most prominent exchanges, second only to Mt. Gox in trading volume and user trust. On February 13, 2012, the
BTCex Exchange Users Discover 83% Bitcoin Missing After Temporary Closure
Exchange custody
Blocked 2011
BTCex was a Russian-based cryptocurrency exchange founded in September 2010 that facilitated trades between bitcoin and fiat currencies including Russian Rubles
MyBitcoin.com Custody Collapse (July 2011): 78,747 BTC Lost, Partial Refund, Operator Never Identified
Exchange custody
Blocked 2011
MyBitcoin.com, launched in 2010, became one of the first popular custodial Bitcoin web wallet services at a time when hardware wallets did not exist and self-cu
50btc Pool Mining Loss: 2–3 BTC Trapped in Defunct Pool, Virtual Disk Recovery Failed
Exchange custody
Indeterminate 2010
In 2010, a user identified as Zagal downloaded and ran 50miner, a mining client for the 50btc pool, on his personal computer for approximately one week. During
3,000 BTC Locked on Discontinued Blockchain.com Wallet: Missing Email Address Blocks Recovery
Exchange custody
Blocked 2009
Ice22 acquired 3,000 BTC in June 2009 through an intermediary claiming to represent a Swiss or Swedish Bitcoin promotion entity. The acquisition process include
GreenAddress User Locked Out by 2FA Requirement Despite Mnemonic Backup
Collaborative custody
Constrained
A GreenAddress user transferred Bitcoin from Bitfinex to a GreenAddress multisig wallet, securing an encrypted backup of their recovery mnemonics using their Br
Bitstamp Withdrawal Blocked: Impossible KYC Demand for Historical Coin Provenance
Exchange custody
Blocked
A user with an established, verified Bitstamp account took a multi-year break from trading. In 2013, the user purchased $2,500 worth of Bitcoin on an alternativ
Coinkite Platform Shutdown: Encrypted Private Key Available, Recovery Status Indeterminate
Exchange custody
Indeterminate
In 2014, a Bitcoin newcomer purchased BTC via Coinkite, an online hosted wallet service. The user then disengaged entirely from cryptocurrency for several years
Federal Seizure of James Zhong's 50,000 Bitcoin Following Theft Conviction
Unknown custody system
Blocked
James Zhong was convicted and sentenced to one year in federal prison for theft of Bitcoin from seized Silk Road proceeds. Federal authorities recovered approxi
Vinny Troia: Coinbase Account Frozen Over Compliance Interpretation
Exchange custody
Blocked
In 2017, Vinny Troia, a professional security consultant and white-hat hacker, purchased Bitcoin on Coinbase and found his account suspended shortly thereafter.
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 a Deceased Father's 14 BTC from Blockchain.com via Email Access
Exchange custody
Survived
A Reddit user reported successfully recovering 14 BTC held in a Blockchain.com wallet belonging to their deceased father approximately six months after the deat
Celsius Chapter 11: User Lost 1 BTC After Collateralized Loan Freeze
Exchange custody
Blocked
A user took out a loan against Bitcoin held on Celsius Network, a custodial lending platform that offered yield and credit facilities. The user's Bitcoin served
← PreviousNext →
Structural dependencies
By stress condition
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