CustodyStress
Archive › Browse by era and custody type › Early Bitcoin (2009–2013) — Exchange custody
Part of the CustodyStress archive of observed Bitcoin custody incidents
Early BitcoinExchange custody

Early Bitcoin (2009–2013) — Exchange custody

Exchange custody failures from Early Bitcoin (2009–2013). Early exchanges operated with minimal security. The failures that culminated in the Mt. Gox collapse were established during this period.

35 cases from this period are included in this archive. Exchange and custodial custody failures account for 100% of cases. 65% of determinate cases resulted in a blocked outcome.

17
Blocked
8
Constrained
1
Survived
9
Indeterminate

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

35 observed cases
Blocked
17 (49%)
Constrained
8 (23%)
Survived
1 (3%)
Indeterminate
9 (26%)
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
Bitomat.pl Exchange Loses 17,000 BTC to AWS Instance Restart
Exchange custody
Constrained 2011
Bitomat.pl operated as the third-largest Bitcoin exchange globally and the largest in Poland during the early 2011 cryptocurrency market. On July 26, 2011, 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
← PreviousNext →
Browse by era and custody type
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.