Part of the CustodyStress archive of observed Bitcoin custody incidents
Bitcoin Exchange Bankruptcy — Documented Cases
Documented cases in the archive where Bitcoin held on an exchange became inaccessible or partially recoverable following the exchange's insolvency, regulatory closure, or operational failure. These cases describe what occurred — the structural conditions, the recovery paths attempted, and the outcomes achieved.
Exchange bankruptcy is a distinct failure mode from exchange hacks or exit scams. In a bankruptcy case, the institution's failure is documented and subject to legal process — but that process takes time, produces uncertain distributions, and often returns less than the original holding. The archive includes exchange collapses where the failure mechanism was insolvency, liquidity failure, or regulatory action rather than fraud or theft.
Archive observations — exchange bankruptcy cases
37%
constrained (partial recovery)
What the archive documents about this scenario
178 documented cases in the archive involve this scenario.
61% of determinate cases resulted in blocked access. 2% resulted in access recovered.
Exchange bankruptcy cases are defined by a structural property: the institution holding the Bitcoin ceases to function before or during recovery. 7% of cases in this category involve a bankruptcy claims process as the documented recovery path — meaning recovery, where it occurs, depends on the outcome of formal insolvency proceedings rather than direct access to the held Bitcoin.
Structural characteristics of exchange bankruptcy failures
Exchange custody is the only Bitcoin custody type where the failure mechanism originates entirely outside the holder's control. In self-custody failures, the holder's own arrangements — lost seed phrases, undocumented procedures, device failures — produce the access barrier. In exchange bankruptcy, the institution fails as a unit and takes all customer holdings with it into insolvency proceedings.
The custody structure of exchange holdings is relevant to outcomes. Exchanges that held Bitcoin in segregated accounts — maintaining a one-to-one correspondence between customer claims and Bitcoin on-chain — produced different outcomes than exchanges that commingled customer assets with operational funds or used customer assets for lending. The archive documents cases across both structures.
Recovery timelines in exchange bankruptcy cases are measured in years, not weeks. Mt. Gox creditors waited over a decade. Celsius creditors received distributions after approximately two years of proceedings. QuadrigaCX creditors received a small fraction of claims after three years. The constrained outcome category in these cases describes eventual partial recovery — not recovery that was available when needed.
A distinct subset of exchange bankruptcy cases involves exchanges that failed due to fraud or theft by operators rather than genuine insolvency — QuadrigaCX is the most documented example in the archive. In these cases, the exchange's stated Bitcoin holdings were inflated or nonexistent, meaning the claims process distributes against a smaller pool of actual assets than creditors believed existed. These cases produce the lowest recovery rates in the category.
Major documented exchange failures
The archive includes dedicated event pages for the largest documented exchange failures:
178 documented cases in this category
Outcome terms
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.
Assessment terms
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
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?
Inclusion requirements
A case must satisfy all three of the following to be included:
- 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.
- 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.
- 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.
In scope
- 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
Out of scope
- 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
Source and verification
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.
Translate