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%)
43.6 BTC Recovered via RoboForm RNG Reverse-Engineering After TrueCrypt Corruption
Software wallet
Survived 2013
Michael, a European Bitcoin holder, generated and secured a 20-character password using RoboForm in April 2013 and transferred 43.6 BTC into a software wallet.
Armory Wallet Synchronization Failure: Access Restored After Software Upgrade
Software wallet
Survived 2013
In October 2013, a BitcoinTalk user holding approximately 0.1008 BTC in an encrypted Armory wallet encountered a critical access failure. The user possessed bot
Bitfloor Exchange Closure March 2013: Banking Relationship Failure After Prior Hack
Exchange custody
Constrained 2013
Bitfloor, a US-based Bitcoin exchange, announced permanent closure on March 17, 2013, after its banking partner terminated the exchange's account without explan
Cryptsy Exchange Collapse: Concealed Hack Left Users Holding Worthless Balances
Exchange custody
Blocked 2013
Cryptsy emerged as the dominant altcoin exchange during the 2013 cryptocurrency boom, facilitating trading in Litecoin, Dogecoin, Feathercoin, and hundreds of a
CoinLab vs. Mt. Gox: Partnership Collapse Traps North American Customer Bitcoin in Legal Limbo (May 2013)
Exchange custody
Blocked 2013
In 2012, Mt. Gox and CoinLab signed a partnership agreement under which CoinLab would assume management of Mt. Gox's US and Canadian customer operations, includ
Encrypted wallet.dat passphrase mismatch: offline wallet creation to recovery (2013)
Software wallet
Survived 2013
In July 2013, a user created an encrypted wallet on an Ubuntu live CD and stored the wallet.dat file offline. Several months later, in December 2013, he importe
Matthew Moody: Bitcoin Miner Dies in Plane Crash, Wallet Inaccessible
Software wallet
Blocked 2013
Matthew Moody was an early Bitcoin miner who began accumulating coins during the network's nascent period when mining remained feasible on standard consumer har
DHS Seizure of Mt. Gox Dwolla and Wells Fargo Accounts (May 2013)
Exchange custody
Blocked 2013
On May 15, 2013, the US Department of Homeland Security, acting through Immigration and Customs Enforcement, seized approximately $2.9 million from Mt. Gox's Dw
Instawallet Hosted Wallet Shutdown After 2013 Security Breach: Partial User Reimbursement
Exchange custody
Constrained 2013
Instawallet, operated by French company Paymain (later Paymium), provided frictionless Bitcoin access during the early ecosystem's rapid expansion. The service
Kristoffer Koch Recovers Forgotten 5,000 BTC Wallet After Four Years
Software wallet
Survived 2013
In 2009, Kristoffer Koch, a Norwegian engineering student, purchased 5,000 Bitcoin for approximately 150 Norwegian kroner (roughly $27 USD at the time) as resea
Blockchain.info iOS App Private Key Corruption: Developer Assisted One User, Denied Another
Exchange custody
Blocked 2013
In April 2013, a blockchain.info iOS app user transferred Bitcoin from Mt. Gox to a newly created address via blockchain.info's mobile application. The transact
Noitev's Lost Electrum Password: 1.8–1.9 BTC Recovered via Brute-Force Attack
Software wallet
Constrained 2013
On April 8, 2013, BitcoinTalk user Noitev reported losing access to an Electrum wallet holding approximately 1.8–1.9 BTC due to a forgotten password. The wallet
Bitcoin-Qt Wallet Loss: Executable Backup Without Private Key File (2013)
Software wallet
Blocked 2013
TheD1ceMan, a forum user, experienced an irrecoverable loss of approximately 1.8 BTC (valued at $2,300–$2,700 USD at May 2013 market prices) due to a critical m
James Howells and the Landfill Bitcoin: Device Lost, Recovery Legally Blocked
Software wallet
Blocked 2013
James Howells, a UK resident, discarded a hard drive containing an encrypted Bitcoin wallet during a routine office clearance in 2013. The device was disposed o
Australian Miner Loses Early Bitcoin When Sole USB Backup Drive Fails Irrecoverably
Software wallet
Blocked 2013
Alex, an Australian Bitcoin miner based in Melbourne, mined Bitcoin around 2010 when mining was still a hobbyist activity with negligible monetary value. Unlike
Bomben Recovers 2013 Bitcoin Wallet Locked by Nonstandard Private Key Encoding
Software wallet
Survived 2013
Bomben created a Bitcoin wallet in 2013 using software that implemented a nonstandard encoding for private keys, diverging from the Wallet Import Format (WIF) s
Mt. Gox SEPA Withdrawal Delayed 28 Days: lukcoin's Unresolved Case (May 2013)
Exchange custody
Indeterminate 2013
On May 7, 2013, BitcoinTalk user lukcoin posted in the Mt. Gox withdrawal delays thread describing a SEPA transfer initiated on April 9 that had not arrived aft
Maxime: Hard Drive Corruption Destroyed Only Copy of Seed Phrase
Software wallet
Blocked 2013
Maxime, a Canadian journalist, began mining Bitcoin during the 2012–2013 period when the technology represented an emerging alternative financial system. He suc
Mt. Gox Bitcoin Withdrawal Crisis: Weeks-Long Delays Signal Terminal Operational Failure
Exchange custody
Blocked 2013
By November 2013, Mt. Gox customers attempting to withdraw Bitcoin faced indefinite waiting periods, a critical escalation from earlier fiat-only delays. What h
Matthew Moody: Early Bitcoin Miner Dies in Plane Crash, Estate Inaccessible
Exchange custody
Blocked 2013
Matthew Philip Moody, 26, of San Ramon, California, was an early Bitcoin miner who accumulated coins during the network's early years using his home computer. O
Dave Kleiman Estate vs. Craig Wright: 1.1 Million Bitcoin, Ownership Unresolved
Unknown custody system
Blocked 2013
Dave Kleiman, a computer forensics specialist based in Florida, was an early Bitcoin developer who died on April 26, 2013, after years of declining health follo
Inputs.io Hack: 4,100 BTC Stolen, Partial Refunds October 2013
Exchange custody
Constrained 2013
Inputs.io was an Australian-hosted Bitcoin wallet service operated by a developer known as TradeFortress. On October 23, 2013, the platform suffered a security
Blockchain.info Web Wallet: Imported Private Key Vanished After Sync Popup
Exchange custody
Blocked 2013
In February 2013, a BitcoinTalk user (BurtW) generated a vanity address using vanitygen and imported the private key into his Blockchain.info web wallet account
Blockchain.info Hosted Wallet Recovery: Password Reset via Seed Phrase (2013)
Exchange custody
Survived 2013
PandaNL opened a Blockchain.info hosted wallet in 2013 and over several years forgot the account password. The user retained three critical pieces of recovery i
Multibit Wallet Recovered From Formatted Hard Drive After 5 Years
Software wallet
Survived 2013
In 2013, a Bitcoin holder stored funds in a Multibit wallet on a work desktop computer. The hard drive was subsequently formatted, and the user assumed the Bitc
← PreviousNext →
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.

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