Archive › More United States cases › United States — Exchange custody
Part of the CustodyStress archive of observed Bitcoin custody incidents
United States — Exchange custody
Cases from the United States where Bitcoin held on an exchange became inaccessible. US exchange custody failures include major platform insolvencies — FTX, Celsius, Voyager — alongside individual account lockouts.
52% of determinate cases in this country with this custody type resulted in a blocked outcome — 11 points below the global rate of 63% for this custody type. This country accounts for 12% of all archive cases with this custody type. The most common recovery path is exchange support.
94% of determinate cases resulted in blocked or constrained access.
33 observed cases
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
Bitfloor Exchange Closure March 2013: Banking Relationship Failure After Prior Hack
Exchange custody
Constrained
2013
Bitfloor, a US-based Bitcoin exchange, announced permanent closure on March 17, 2013, after its banking partner terminated the exchange's account without explan
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
DHS Seizure of Mt. Gox Dwolla and Wells Fargo Accounts (May 2013)
Exchange custody
Blocked
2013
On May 15, 2013, the US Department of Homeland Security, acting through Immigration and Customs Enforcement, seized approximately $2.9 million from Mt. Gox's Dw
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
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
Lost Access to Blockchain.info Wallet Without Identifier or Mnemonic
Exchange custody
Indeterminate
A disabled user in the United States was introduced to Bitcoin by their son, who created two blockchain.info wallets and taught them to use faucets as an activi
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.