CustodyStress
Archive › Browse by documentation and stress › Present and Interpretable — Vendor lockout
Part of the CustodyStress archive of observed Bitcoin custody incidents
Present And InterpretableVendor lockout

Present and Interpretable — Vendor lockout

Cases where interpretable documentation existed but exchange or platform lockout still blocked access. Documentation sufficiency does not protect against institutional failure — the barrier was the platform, not the holder's knowledge.

107 cases in this intersection. 55% of determinate cases resulted in a blocked outcome and 3% in access survived. The most common recovery path is exchange support.

57
Blocked
43
Constrained
3
Survived
4
Indeterminate

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

107 observed cases
Blocked
57 (53%)
Constrained
43 (40%)
Survived
3 (3%)
Indeterminate
4 (4%)
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
Cryptsy Exchange Insolvency: 2014 Hack Concealed Until 2015 Withdrawal Freeze
Exchange custody
Constrained 2015
Cryptsy, a Florida-registered multi-currency exchange founded in 2013, suffered a significant security breach in 2014 that compromised user Bitcoin and altcoin
796 Exchange — 1,000 BTC Stolen via Withdrawal Address Redirect (January 2015)
Exchange custody
Blocked 2015
796 was a Chinese cryptocurrency exchange offering spot and futures trading. In late January 2015, the platform discovered a security breach in which an attacke
Vircurex Withdrawal Freeze: Timothy Shaw's 12.85 BTC Locked Since 2014
Exchange custody
Blocked 2015
Timothy Shaw, a Colorado resident, executed a trade on Vircurex on March 24, 2014, converting his entire dogecoin balance into 12.85 BTC. That same morning, Vir
Vault of Satoshi Exchange Closure: Institutional Custody Dependency and Forced Withdrawal Deadline
Exchange custody
Constrained 2015
Vault of Satoshi, a Canadian cryptocurrency exchange launched in October 2013, announced permanent closure effective February 5, 2015. The platform had differen
Institutional lockout — exchange custody, Australia (2015)
Exchange custody
Blocked 2015
igot, an Australian-branded Bitcoin exchange later traced to operational infrastructure in India, faced a significant customer crisis in May 2015 when users rep
Digital CC v. igot Exchange: $180,000 Bitcoin Claim, Australian Court Action
Exchange custody
Indeterminate 2015
Digital CC, an Australian digital currency company, accumulated approximately $180,000 in Bitcoin holdings or claims held on the igot exchange. Beginning in 201
MintPal/Moolah Exchange Collapse: 3,700 BTC Inaccessible After Ryan Kennedy's Exit Scam
Exchange custody
Blocked 2015
MintPal was a prominent altcoin exchange serving tens of thousands of users in 2014. Following a July 2014 hack that cost approximately $2 million in VeriCoin,
Institutional lockout — exchange custody, Australia (2015)
Exchange custody
Constrained 2015
igot, an Australian Bitcoin exchange operated by Remi Fabre under the digital.cc domain, entered a state of operational dysfunction beginning in August 2015. Us
Kraken Exchange DDoS Attack — Users Locked Out During November 2015 Extortion Siege
Exchange custody
Constrained 2015
Kraken, a US-registered cryptocurrency exchange founded in 2011, received an extortion letter in November 2015 demanding Bitcoin payment in exchange for cancell
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
Otohs: 76 BTC Withdrawal Request Refused by Insolvent Cryptsy (October 2015)
Exchange custody
Blocked 2015
On October 5, 2015, a Reddit user identified as Otohs submitted a withdrawal request for 76 BTC from his verified Cryptsy account, which carried no withdrawal l
Cryptsy Inactive Account Bitcoin Disappearance (2015)
Exchange custody
Blocked 2015
In 2015, a Bitcoin holder registered on Cryptsy after acquiring Dogecoin, which they subsequently traded for Bitcoin. The account remained dormant for over a ye
Institutional lockout — exchange custody, Australia (2015)
Exchange custody
Constrained 2015
In August 2015, the Australian Bitcoin exchange igot ceased all operations and communications, leaving customers unable to access their holdings or funds. Reddi
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
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
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
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
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
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
← PreviousNext →
Browse by documentation 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