CustodyStress
Archive › Browse by halving cycle and stress › Halving Cycle 2 (2013–2016) — Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
Cycle 2Passphrase unavailable

Halving Cycle 2 (2013–2016) — Passphrase unavailable

Passphrase failures from Halving Cycle 2 (2013–2016). As hardware wallets became available and BIP39 was standardised, the first wave of forgotten passphrase cases emerged.

68 cases in this intersection. 38% of determinate cases resulted in a blocked outcome and 42% in access survived. The most common recovery path is password bruteforce.

9
Blocked
5
Constrained
10
Survived
44
Indeterminate

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

68 observed cases
Blocked
9 (13%)
Constrained
5 (7%)
Survived
10 (15%)
Indeterminate
44 (65%)
Lost Blockchain.info iOS Wallet Password (2014) — Recovery Attempt via BTCRecover
Exchange custody
Indeterminate 2014
In December 2021, a BitcoinTalk user identified as Quix77 disclosed loss of access to a Blockchain.info wallet created in August 2014 via the iOS Blockchain app
Forgotten Blockchain.info Password: 0.22 BTC Trapped Behind AES Encryption
Exchange custody
Indeterminate 2014
On October 8, 2014, a BitcoinTalk forum user findftp described his friend's predicament: access lost to a Blockchain.info wallet containing 0.22 BTC due to a fo
Electrum Desktop Wallet: 0.7 BTC Locked by Forgotten Password, Missing Seed Phrase
Software wallet
Indeterminate 2014
Liam, a new Bitcoin user (BitcoinTalk username AbeTheCat), purchased 0.7 BTC in October 2014 and stored it in an Electrum desktop software wallet on his origina
Password Safe Crash Leaves Blockchain.info Wallet Inaccessible
Exchange custody
Indeterminate 2014
In January 2014, a BitcoinTalk user identified as StinkyS4L discovered that their Password Safe application had crashed, rendering all stored passwords inaccess
Paper Wallet Private Key Recovery: Reconstructing Corrupted Font-Rendered WIF
Software wallet
Survived 2014
In 2014, a Bitcoin holder generated a paper wallet using a widely available online paper wallet generator tool. The printed document contained both a public add
BIP38 Passphrase Recovery Service Abandonment (2014)
Software wallet
Indeterminate 2014
In July 2014, a BitcoinTalk forum user identified as houseo posted in the Services section describing a custody access failure involving a forgotten BIP38 passp
KeePass Database Corruption: 11.7 BTC Locked Behind Unrecoverable Password
Software wallet
Indeterminate 2014
In April 2014, a BitcoinTalk user reported that their cousin had lost access to 11.7 BTC held in an encrypted wallet.dat file. The cousin had generated a strong
Forgotten Passphrase: 3.3 BTC Recovered by Third-Party Service for 20% Fee
Software wallet
Constrained 2014
In June 2014, a BitcoinTalk user identified as marsje007 discovered they could no longer access a wallet containing 3.3 BTC after changing the passphrase and fa
Payment Processor: Passphrase Lost on Damaged Flash Drive, 200+ BTC Addresses at Risk
Software wallet
Constrained 2014
In June 2014, an operator running a Bitcoin payment processing system discovered that the flash drive storing the passphrase to their wallet had been irreversib
22.1 BTC Bitcoin-Qt Wallet Password Recovery via Community Brute Force (2014)
Software wallet
Survived 2014
In November 2014, a Bitcoin-Qt wallet containing 22.1 BTC became inaccessible when its owner forgot the passphrase. The owner had documented the password creati
Forgotten Password on Blockchain.info Web Wallet: 0.22 BTC Inaccessible
Exchange custody
Indeterminate 2014
In October 2014, a Bitcoin Forum user (findftp) sought technical assistance for a friend who had lost access to a Blockchain.info wallet containing 0.22 BTC (ap
Forgotten Blockchain.info Password: 0.22 BTC Recovery Attempt via Brute-Force
Exchange custody
Indeterminate 2014
In October 2014, a BitcoinTalk forum user (findftp) posted on behalf of a friend who had lost the password to a Blockchain.info web wallet containing 0.22 BTC (
Blockchain.com 2014 Hosted Wallet: Password and Seed Phrase Loss
Exchange custody
Indeterminate 2014
A Blockchain.com customer acquired approximately 0.5 BTC in 2014 using the platform's hosted wallet service. Over the years, the original password and recovery
Forgotten Encryption Passphrase Blocks Access to 10+ BTC in Bitcoin Core Wallet
Software wallet
Indeterminate 2014
In December 2014, a BitcoinTalk user identifying as casperround publicly sought help recovering access to an encrypted Bitcoin Core wallet containing over 10 BT
Forgotten Password on Blockchain.info: 0.22 BTC Access Lost, Brute-Force Recovery Attempted
Exchange custody
Indeterminate 2014
In October 2014, a BitcoinTalk forum user reported that their friend had become locked out of a blockchain.info wallet containing 0.22 BTC after forgetting the
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
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
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
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
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
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
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
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
BitcoinTalk User RTQ1154 Locks 78 BTC Behind Mistyped Wallet Password
Software wallet
Indeterminate 2013
In June 2013, a BitcoinTalk forum user identifying as RTQ1154 posted in a community thread titled 'Let's add up the KNOWN lost bitcoins' describing a custody lo
← PreviousNext →
Browse by halving cycle 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