CustodyStress
Archive › Browse by era and custody type › Exchange Era (2014–2019) — Exchange custody
Part of the CustodyStress archive of observed Bitcoin custody incidents
Exchange EraExchange custody

Exchange Era (2014–2019) — Exchange custody

Exchange custody failures from the Exchange Era (2014–2019). This is the dominant combination in the archive — the period when exchange custody became the primary access model and produced the largest volume of institutional failures.

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

61
Blocked
34
Constrained
6
Survived
38
Indeterminate

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

139 observed cases
Blocked
61 (44%)
Constrained
34 (24%)
Survived
6 (4%)
Indeterminate
38 (27%)
ThrillHou v. Cryptsy: Account Lockout, KYC Data Misuse, and Alleged Identity Compromise
Exchange custody
Blocked 2015
ThrillHou, a Cryptsy user, experienced repeated account lockouts beginning in 2015. When support staff operating under aliases BigJohn and John McPherson repeat
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
Forgotten Blockchain.info Password: Client-Side Encryption Locks €100 Bitcoin Permanently
Exchange custody
Blocked 2015
On September 17, 2015, a Blockchain.info user with the forum username Seporstia posted requesting help recovering access to a hosted wallet after forgetting the
Blockchain.info Account Lockout: Forgotten Password, Missing Seed Phrase, $3,800 USD Inaccessible
Exchange custody
Indeterminate 2015
TheLoser created a hosted wallet on Blockchain.info via the Apple mobile application in late September 2015. The wallet creation process did not present or prov
Cryptsy Freezes 175 BTC: Ukrainian User Blocked by KYC During Armed Conflict
Exchange custody
Blocked 2015
In 2015, a Reddit user known as alkinsonf held 175 Bitcoin on the popular exchange Cryptsy following an active trading period with no apparent issues. Without w
Blockchain.com 2015 Private Key Encoding Bug: 0.48 BTC Permanently Inaccessible
Exchange custody
Indeterminate 2015
In August 2022, a user identified as montythegoat discovered an old Blockchain.com wallet on their Google Drive while cleaning archived files. The wallet had be
Coinbase Bitcoin Inheritance Without Estate Plan or Recovery Instructions
Exchange custody
Indeterminate 2015
A Bitcoin advocate died by suicide in March, leaving approximately $15,000 USD in Bitcoin held on Coinbase. The deceased had not designated a recovery contact,
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
Blockchain.info iOS Wallet: $3,600 Lost to Missing Mnemonic and Unresettable Password
Exchange custody
Blocked 2015
In September 2015, TheLoser created a Bitcoin wallet on Blockchain.info using an iOS mobile device. Unlike documented Blockchain.info workflows, the wallet crea
0.3 BTC Lost After Uninstalling Blockchain.info Desktop Wallet Without Backup
Exchange custody
Blocked 2015
In June 2015, a user identified as Williams2017 received approximately 0.3 BTC (then valued at roughly $70 USD) from an entity called 'www.instantgold.ng' to th
Cryptsy November 2015: Three Frozen Withdrawals, Unresponsive Support, Hidden Insolvency
Exchange custody
Blocked 2015
In November 2015, a Cryptsy user publicly identified as Bitcointard filed detailed complaints across The Merkle, Reddit, and Bitcointalk forums describing three
Recovery of Dormant Blockchain.info Wallet via Legacy 20-Word Mnemonic (2017)
Exchange custody
Survived 2014
Roland808, a BitcoinTalk user, discovered a text file on their computer in March 2017 dated from 2014 containing a label 'bitcoin nmemonic' followed by 20 rando
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
Lost Blockchain.info iOS Wallet Password (2014) — Recovery Attempt via BTCRecover
Exchange custody
Indeterminate 2014
In December 2021, a BitcoinTalk user identified as Quix77 disclosed loss of access to a Blockchain.info wallet created in August 2014 via the iOS Blockchain app
Forgotten Blockchain.info Password: 0.22 BTC Trapped Behind AES Encryption
Exchange custody
Indeterminate 2014
On October 8, 2014, a BitcoinTalk forum user findftp described his friend's predicament: access lost to a Blockchain.info wallet containing 0.22 BTC due to a fo
MtGox Civil Rehabilitation Claims Process: Password Reset Barrier
Exchange custody
Constrained 2014
Following the MtGox collapse, Japan's civil rehabilitation framework opened a formal claims process to distribute recovered assets to affected users. However, a
Password Safe Crash Leaves Blockchain.info Wallet Inaccessible
Exchange custody
Indeterminate 2014
In January 2014, a BitcoinTalk user identified as StinkyS4L discovered that their Password Safe application had crashed, rendering all stored passwords inaccess
Lost Access to 2014 blockchain.info Wallets: Non-Standard Recovery Mnemonics, No Support Response
Exchange custody
Indeterminate 2014
In July 2020, forum user gbola reported locating five recovery mnemonics created circa 2014 when blockchain.info was in its early operations. The user's entire
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
Blockchain.info Two-Factor Authentication Reset Declined — November 2014
Exchange custody
Constrained 2014
On November 15, 2014, a Blockchain.info user enabled two-factor authentication using Google Authenticator on an Android phone but failed to back up the QR code
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
Cryptsy Exchange: 13,000 BTC Theft Concealed 18 Months, Customer Funds Lost
Exchange custody
Blocked 2014
Cryptsy was a cryptocurrency exchange operating in the early 2010s that suffered a critical security breach in July 2014. A developer associated with Lucky7Coin
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
← 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.

Original text
Rate this translation
Your feedback will be used to help improve Google Translate