CustodyStress
Archive › Browse by trigger and era › Institutional Failure — Exchange Era (2014–2019)
Part of the CustodyStress archive of observed Bitcoin custody incidents
Institutional_failureExchange Era

Institutional Failure — Exchange Era (2014–2019)

Institutional failure cases from the Exchange Era (2014–2019). Mt. Gox, QuadrigaCX, and the era's exchange failures define this category.

37 cases in this intersection. 50% of determinate cases resulted in a blocked outcome. The most common recovery path is exchange support.

16
Blocked
16
Constrained
0
Survived
5
Indeterminate

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

37 observed cases
Blocked
16 (43%)
Constrained
16 (43%)
Indeterminate
5 (14%)
KipCoin Exchange Linode Hosting Compromise: October 2014 Breach, February 2015 Disclosure
Exchange custody
Indeterminate 2015
KipCoin operated as a custodial Bitcoin exchange running infrastructure on Linode virtual private servers. In June 2014, Linode suffered a security breach that
Bitstamp Exchange Hack — 19,000 BTC Stolen via Employee Phishing, January 2015
Exchange custody
Constrained 2015
On January 4, 2015, Bitstamp discovered that operational hot wallets held approximately 19,000 BTC had been compromised. The Luxembourg-based exchange, a primar
Bitfinex May 2015 Hot Wallet Breach: 1,400 BTC Stolen, Trading Suspended
Exchange custody
Constrained 2015
Bitfinex, a major cryptocurrency exchange operating under Hong Kong incorporation and British Virgin Islands registration, suffered a security breach in May 201
BTER Cold Wallet Compromise: 7,170 BTC Stolen, Exchange Suspended (February 2015)
Exchange custody
Blocked 2015
BTER, a Chinese cryptocurrency exchange, suffered a critical custody failure in February 2015 when its cold wallet—the repository for user Bitcoin deposits and
CAVIRTEX Closure and Withdrawal Delays: February–March 2015
Exchange custody
Constrained 2015
CAVIRTEX, a Canadian Bitcoin exchange, announced its closure on February 17, 2015, following discovery of a database compromise involving older user information
Mt. Gox Exchange Collapse: 750,000 Bitcoin Trapped After February 2014 Withdrawal Halt
Exchange custody
Blocked 2014
Mt. Gox, the world's largest Bitcoin exchange at the time, announced a complete halt to all Bitcoin withdrawals on February 7, 2014. The exchange attributed the
MintPal Exchange: 3,701 BTC Theft by Operator Ryan Kennedy (2014)
Exchange custody
Blocked 2014
Ryan Kennedy, operating under the alias Alex Green with a public presence in the Dogecoin community, acquired MintPal—a mid-tier altcoin exchange—in mid-2014. T
Mt. Gox Exchange Collapse: 850,000 BTC Lost, 127,000 Creditors Locked Out
Exchange custody
Constrained 2014
Mt. Gox operated as the dominant Bitcoin exchange in early 2014, processing over 70% of global Bitcoin transactions. On February 7, 2014, the platform abruptly
Vircurex Exchange Freezes Bitcoin Withdrawals, 1,666 BTC Remains Inaccessible
Exchange custody
Blocked 2014
Vircurex, founded in October 2011, operated as a custodial cryptocurrency exchange with servers in Beijing but registered falsely as a Belize entity—later deter
BitInstant Exchange Collapse: Charlie Shrem Arrest Freezes Customer Funds
Exchange custody
Blocked 2014
BitInstant operated as one of the earliest and most prominent custodial Bitcoin exchanges in the United States, co-founded by Charlie Shrem with backing from th
Picostocks Bitcoin Exchange: 7,196 BTC Lost to Insider Theft (2013–2014)
Exchange custody
Blocked 2014
Picostocks was a custodial Bitcoin exchange that allowed users to hold Bitcoin-denominated shares in various projects. The platform suffered two major theft inc
FXBTC Shanghai Exchange Premature Closure Blocks Customer Withdrawals
Exchange custody
Blocked 2014
FXBTC was a Shanghai-based cryptocurrency exchange operating during China's early Bitcoin trading boom. In early May 2014, following escalating regulatory press
← PreviousNext →
Browse by trigger and era
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