CustodyStress
Archive › Bitcoin eras › Early Bitcoin (2009–2013)
Part of the CustodyStress archive of observed Bitcoin custody incidents

Early Bitcoin (2009–2013)

Bitcoin custody failures from the network's first five years. Custody infrastructure was nonexistent — no hardware wallets, no seed phrase standards, no established backup practices. The dominant failure modes are device loss, discarded hard drives, and seeds that were never recorded. Coercion had not yet emerged as a significant pattern.

158 cases from this period are included in this archive. 73% of determinate cases resulted in a blocked outcome. The most frequently observed stress condition is passphrase-unavailable cases.

Archive analysis — 158 cases
Outcomes
73% of determinate cases resulted in blocked access, close to the archive-wide average of 69%.
Documentation coverage
46% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
75% of cases involved software wallet, followed by exchange custody at 22%.
Recovery path
Password Bruteforce is the most documented recovery path (31 cases, 20% of subset). Of those with a determinate outcome, 73% resulted in recovered or constrained access.
Documentation
42% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Structural dependency
73% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
62
Blocked
9
Constrained
14
Survived
73
Indeterminate

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

158 observed cases
Blocked
62 (39%)
Constrained
9 (6%)
Survived
14 (9%)
Indeterminate
73 (46%)
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In November 2013, BitcoinTalk user eric89 reported a custody failure involving a Litecoin wallet mined in April 2013. The user had encrypted the wallet using Li
Armory Wallet Lost via VirtualBox Snapshot Rollback—Binary Recovery Attempt
Software wallet
Indeterminate 2013
In October 2013, a BitcoinTalk user known as HowlingMad lost access to 6.59159344 BTC stored in Armory, a then-leading Bitcoin wallet application running on Win
Mt. Gox Withdrawal Crisis: levino's 347-Page Thread Documents SEPA Delays (April 2013)
Exchange custody
Constrained 2013
On April 18, 2013, BitcoinTalk user levino initiated a withdrawal of Euro proceeds from Mt. Gox, the world's largest Bitcoin exchange at that time. After 14 day
Encrypted Wallet Recovery After Accidental Partition Deletion (2013)
Software wallet
Indeterminate 2013
On July 17, 2013, a Bitcoin holder identified as Praxis posted to a cryptocurrency forum after losing access to multiple wallet files stored in hidden Linux dir
1,000 BTC Permanently Lost After Brother Deletes wallet.dat From Shared Dropbox Folder
Software wallet
Blocked 2013
In 2017, Hacker News user illumin8 disclosed a permanent loss of 1,000 BTC resulting from a wallet file deletion in a shared Dropbox folder. The Bitcoin wallet
2013 Electrum Wallet File Blocked by Version Incompatibility
Software wallet
Indeterminate 2013
SirKhaal, a Bitcoin holder from the early mining era, retained an Electrum wallet file (electrum.dat) from 2013 along with its original passphrase. When attempt
Passphrase unavailable — software wallet (2013)
Software wallet
Indeterminate 2013
On February 5, 2014, BitcoinTalk user repukken posted in the encrypted wallet recovery thread seeking help to brute-force access to a Dogecoin wallet after forg
Bitcoin-Qt 0.8.0-beta Wallet Corruption on OS X Mountain Lion — Unrecovered After Five Months
Software wallet
Blocked 2013
In late April 2013, jordan.dev, a Bitcoin-Qt user on macOS Mountain Lion 10.8.3, encountered a crash (EXC_BAD_ACCESS/SIGBUS) when launching Bitcoin-Qt 0.8.0-bet
Blockchain.info Hosted Wallet Lockout: Decryption Error and Recovery via Desktop Import
Exchange custody
Indeterminate 2013
In March 2013, a Blockchain.info user ('key2') encountered a critical access failure on the platform's hosted wallet service shortly after their first Bitcoin p
BTC Guild Miner's Lost Self-Custody Wallet: 0.05 BTC Inaccessible Without Seed or Backup File
Software wallet
Indeterminate 2013
In 2013–2014, user haihong8787 mined Bitcoin using a graphics card on the BTC Guild mining pool (user ID 97249). The pool distributed mining rewards directly to
James Howell's 8,000 Bitcoin Hard Drive: Landfill Loss Without Backup
Software wallet
Blocked 2013
James Howell, a computer professional based in Wales, accumulated approximately 8,000 Bitcoin during the early mining era through a combination of mining and ac
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.
Dogecoin Wallet Passphrase Mismatch: 50,000 DOGE Inaccessible Despite Documentation
Software wallet
Indeterminate 2013
On December 27, 2013, a BitcoinTalk user named Alohaboy posted seeking help recovering access to a Dogecoin wallet. The user had documented their passphrase ('d
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
13.8 BTC Lost to Forgotten Wallet.dat Password: DIY and Professional Recovery Attempts
Software wallet
Indeterminate 2013
A Bitcoin user created an encrypted Bitcoin Core wallet in 2013 containing 13.8 BTC. The passphrase was forgotten, rendering the wallet inaccessible. In Septemb
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
TrueCrypt Volume Corruption Across All Backups: Wallet Recovery Attempt
Software wallet
Indeterminate 2013
In 2011, a Bitcoin user created two TrueCrypt encrypted containers on Windows 7: one holding wallet.dat, the second holding unimportant files as a control. Afte
← Previous
1237
Next →
Bitcoin eras
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