CustodyStress
Archive › Documentation status › Present and Interpretable
Part of the CustodyStress archive of observed Bitcoin custody incidents

Present and Interpretable

Cases where documentation was available and interpretable but other barriers prevented recovery.

Even where documentation was present and interpretable, 62% of determinate cases resulted in a blocked outcome. Documentation reduces but does not eliminate access failure — in many cases the constraint was technical or institutional rather than informational.

174
Blocked
54
Constrained
51
Survived
20
Indeterminate

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

299 observed cases
Blocked
174 (58%)
Constrained
54 (18%)
Survived
51 (17%)
Indeterminate
20 (7%)
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
Bitcoin Core Wallet Corruption: Selective Key Decryption Failure and Community Recovery
Software wallet
Survived 2015
Henke created an encrypted wallet backup on December 20, 2015, containing approximately 4 BTC. After refreshing his Windows 7 system and reinstalling Bitcoin Co
Deleted Temporary Wallet Recovery via Private Key Forensic Extraction
Software wallet
Survived 2015
In September 2015, a Bitcoin user known as dooglus encountered a self-imposed custody failure during a transaction resend operation. After noticing an unconfirm
Recovering Deleted Bitcoin Core wallet.dat via pywallet: Device Loss and Forensic Key Extraction
Software wallet
Survived 2015
Edgar's Bitcoin Core wallet became inaccessible in 2015 when the wallet.dat file was removed from the active system while the Bitcoin Core client remained open.
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
Zombie Paintball Incident: Written Password Loss Blocks Access to $20K Bitcoin
Software wallet
Blocked 2015
Luke purchased his first Bitcoin around 2013 for approximately $200 and continued accumulating holdings over roughly two years, investing between $15,000 and $2
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
Ryan Piercy Kidnapped in Costa Rica — First Widely Reported Bitcoin Ransom Demand
Unknown custody system
Indeterminate 2015
On January 20, 2015, Ryan Piercy, a Canadian national residing in San José, Costa Rica, was abducted by kidnappers who made an unprecedented demand: $500,000 in
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
OKCoin Halts US Customer Access (August 2015): Regulatory Exclusion
Exchange custody
Constrained 2015
OKCoin, then a top-ten Bitcoin exchange by trading volume, announced on August 31, 2015 that it would cease accepting USD deposits from American users and prohi
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
Hard Drive Format Recovery: 2 BTC Restored via Sector Scanning and wallet.dat Reconstruction
Software wallet
Survived 2015
In approximately 2015, marilyn4325 formatted a hard drive and installed Windows 10, intending to preserve wallet data via backup first. However, the backup beca
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
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
← Previous
167891012
Next →
Documentation status
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.