CustodyStress
Archive › Browse by era and stress › Exchange Era (2014–2019) — Vendor lockout
Part of the CustodyStress archive of observed Bitcoin custody incidents
Exchange EraVendor lockout

Exchange Era (2014–2019) — Vendor lockout

Exchange and platform lockout cases from the Exchange Era (2014–2019). This combination represents the defining failure pattern of the period — concentrated exchange dependency producing mass access failures when platforms collapsed.

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

42
Blocked
26
Constrained
2
Survived
20
Indeterminate

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

90 observed cases
Blocked
42 (47%)
Constrained
26 (29%)
Survived
2 (2%)
Indeterminate
20 (22%)
Bithumb $31 Million Hack — June 2018 Withdrawal Suspension
Exchange custody
Constrained 2018
Bithumb, one of South Korea's dominant cryptocurrency exchanges handling billions in daily trading volume, discovered a security breach on June 19, 2018. Intern
Elvis Cavalic and QuadrigaCX: C$15,000 Withdrawal Lost to Exchange Collapse
Exchange custody
Blocked 2018
Elvis Cavalic of Calgary, Alberta was an active QuadrigaCX customer who had accumulated cryptocurrency holdings through trading on the platform. In October 2018
Zaif Exchange Hack: 5,966 BTC Stolen, User Funds Frozen (September 2018)
Exchange custody
Constrained 2018
On September 14, 2018, the Zaif cryptocurrency exchange operated by Tech Bureau Corp suffered a significant hot wallet breach. Attackers gained unauthorized acc
Xapo Mobile 2FA Lockout: User Without Smartphone Denied Account Access
Exchange custody
Blocked 2017
In August 2017, Xapo transitioned its hosted wallet platform to mandatory two-factor authentication via mobile application. A user (songdove) without a smartpho
Blockchain.info Wallet Access Failure: Platform Login System Change (2017)
Exchange custody
Survived 2017
In March 2014, a user created a Blockchain.info-hosted wallet and received a 12-word recovery passphrase as the sole access credential. The user documented the
7 BTC Lost After Address Disappearance on Blockchain.info Web Wallet
Exchange custody
Indeterminate 2017
In August 2017, a BitcoinTalk forum user reported a significant loss involving approximately 7 BTC stored on Blockchain.info. The user had migrated from Bitcoin
Yapizon Exchange Hack (April 2017): 3,831 BTC Stolen, Socialised Loss Model Applied to All Users
Exchange custody
Blocked 2017
On April 22, 2017, Yapizon, a South Korean cryptocurrency exchange, suffered a security breach resulting in the theft of 3,831 BTC—approximately 37% of the exch
Youbit Exchange Bankruptcy: Second Hack Triggers 75% Fund Recovery Limit
Exchange custody
Constrained 2017
Youbit, operated by South Korean firm Yapian, experienced two significant security breaches during 2017. The first attack in April 2017 compromised approximatel
Blockchain.info Second Password Loss: Vendor Lockout Without Recovery Mechanism
Exchange custody
Indeterminate 2017
In January 2017, forum user ericblogs reported inability to execute transactions on a Blockchain.info hosted wallet after forgetting the account's second passwo
David Vu's Blockchain.info Wallet: Trapped With 2 BTC, Secondary Password Forgotten
Exchange custody
Indeterminate 2017
David Vu discovered a critical access failure in June 2017 when he attempted to withdraw Bitcoin from his Blockchain.info wallet. He retained access to his prim
Institutional lockout — exchange custody (2017)
Exchange custody
Indeterminate 2017
Between 2014 and 2015, the user created cryptocurrency accounts on blockchain.info and retained the mnemonic seed phrases. By December 2017, the user attempted
Kraken Account 2FA Lockout: Support Vanished After ID Verification
Exchange custody
Indeterminate 2017
In September 2017, a Kraken user (z1926) enabled two-factor authentication on their exchange account but encountered a system malfunction during the process. Th
Blockchain.info Legacy Wallet Lockout: 17-Word Phrase Incompatible With Recovery Tool
Exchange custody
Indeterminate 2017
Between November and December 2017, multiple Blockchain.info users discovered they could not access legacy wallets created years earlier, despite possessing com
Blockchain.info Wallet Access Blocked by Lost Wallet ID Despite Valid Recovery Phrase
Exchange custody
Indeterminate 2017
In December 2017, a Bitcoin holder discovered that custody of funds deposited in a Blockchain.info wallet created in early 2013 had become inaccessible despite
Blockchain.info Legacy Wallet Access Failure: 17-Word Recovery Phrase Incompatibility
Exchange custody
Blocked 2017
Beginning in late November 2017, multiple users including Ople, nwankwotech, and Boldos reported simultaneous access failures to Blockchain.info wallets created
Blockchain.info Hosted Wallet Recovery Attempt: Partial Password, No Seed Backup
Exchange custody
Indeterminate 2017
In October 2017, a BitcoinTalk user identified as Parodium reported being locked out of a blockchain.info wallet created years earlier. The user retained email
Blockchain.info 2FA Email Delivery Failure — December 2017 Access Lock
Exchange custody
Constrained 2017
In early December 2017, the user crando discovered they could not access their Blockchain.info hosted wallet after the platform failed to deliver two-factor aut
Custodial Wallet Provider Bankruptcy: 2012 Bitcoin Purchase Permanently Inaccessible
Exchange custody
Blocked 2017
In November 2017, a Bitcoin holder disclosed that they had purchased Bitcoin in 2012 but subsequently lost access to their holdings after the company maintainin
Mycelium Mobile Wallet Balance Access Failure — December 2017
Software wallet
Indeterminate 2017
In mid-December 2017, a Bitcoin user (Myrr) discovered a critical custody access failure in the Mycelium mobile wallet on their iPhone. The user had purchased B
Cryptsy Exchange: 13,000 BTC Theft Concealed, Ponzi Operations, Founder Flight (2014–2016)
Exchange custody
Constrained 2016
Cryptsy, a Florida-based cryptocurrency exchange operated by Paul Vernon (online alias 'Big Vern'), suffered a critical security breach in July 2014 when attack
7.8 BTC Lost in Blockchain.info Interface Failure After Platform Upgrade
Exchange custody
Indeterminate 2016
In February 2016, a user created two cryptocurrency addresses within Blockchain.info's hosted web wallet service and sent test transactions from Bitcoin-Qt to b
Cointrader Exchange Discovers Bitcoin Shortfall, Suspends Operations Indefinitely (March 2016)
Exchange custody
Blocked 2016
Cointrader operated as a Canadian cryptocurrency exchange with modest activity through early 2016, processing approximately 81 BTC in daily trading volume durin
Bitcurex Exchange Collapse: 2,300 BTC Lost, No Customer Database Backups
Exchange custody
Blocked 2016
Bitcurex launched in 2012 as Poland's first and largest Bitcoin exchange, processing over $50 million in BTC transactions during its final six months. The platf
Block.io Custodial Lockout: 2FA Authentication Failure and Support-Dependent Recovery
Exchange custody
Survived 2016
On January 18, 2016, a BitcoinTalk user identified as 'statue' reported being locked out of their Block.io online wallet after entering an incorrect two-factor
Gatecoin Exchange: 250 BTC and 185,000 ETH Drained via Cold Storage Routing Compromise
Exchange custody
Blocked 2016
Gatecoin Limited operated as a Hong Kong-based cryptocurrency exchange from 2013, gaining credibility through backing by the Hong Kong Science and Technology Pa
← PreviousNext →
Browse by era and stress
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