CustodyStress
ArchiveUndocumented Recovery Procedure › Passphrase Unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents

Undocumented Recovery Procedure — Passphrase Unavailable

Cases where no written procedure existed for how recovery would be executed. The holder understood the arrangement; no record existed to guide anyone else. This page shows archive cases where both conditions were present.

75% of all Passphrase Unavailable cases in the archive involve this structural dependency. Among them, 56% of determinate cases resulted in a blocked outcome. The most common recovery path is password bruteforce.

36
Blocked
4
Constrained
24
Survived
105
Indeterminate

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

169 observed cases
Blocked
36 (21%)
Constrained
4 (2%)
Survived
24 (14%)
Indeterminate
105 (62%)
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
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
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
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
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
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In April 2013, a BitcoinTalk user identified as 'veryveryinteresting' posted in topic 85495, the community's primary encrypted wallet recovery thread, describin
BitcoinTalk User 'Liquid': 30 BTC Inaccessible Due to Forgotten Bitcoin-Qt Encryption Password
Software wallet
Indeterminate 2013
In June 2013, a BitcoinTalk forum user operating under the handle 'Liquid' posted in the encrypted wallet recovery thread (topic 85495) describing an inaccessib
Hidden wallet discovered — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In November 2013, BitcoinTalk user nobbie discovered that Bitcoin-Qt's wallet encryption feature had been activated, locking access to the wallet with a passwor
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In April 2013, a BitcoinTalk user identified as 'legitnick' posted in topic 85495, the primary community support thread for locked wallet recovery during the 20
Feathercoin Desktop Wallet Encryption: Community Recovery Estimate vs. Actual Search Space (Nov 2013)
Software wallet
Indeterminate 2013
On 30 November 2013, BitcoinTalk user 'user0244' posted in the encrypted wallet recovery thread seeking assistance with a locked Feathercoin wallet. The user co
Ecurb123: Encrypted Bitcoin-Qt Wallet on Ubuntu, Passphrase Lost, Recovery Blocked by Configuration Barriers
Software wallet
Indeterminate 2013
In December 2013, BitcoinTalk user Ecurb123 posted in the encrypted wallet recovery thread describing a locked Bitcoin-Qt wallet on Ubuntu Linux. The user had s
Passphrase unavailable — software wallet (2013)
Software wallet
Indeterminate 2013
In December 2013, BitcoinTalk user goldbishop posted in the encrypted wallet recovery forum that two altcoin wallets—one holding Protoshares (PTS) and another h
Passphrase unavailable — software wallet (2013)
Software wallet
Indeterminate 2013
On December 26, 2013, BitcoinTalk Senior Member mackminer posted in the encrypted wallet recovery forum describing a locked Bitcoin wallet protected by a multi-
Coinbase Paper Wallet Private Key Lost Before Printing—4.5 BTC Inaccessible
Software wallet
Blocked 2013
In December 2013, a Bitcoin newcomer attempted to move funds to a Coinbase-hosted paper wallet generator. The user copied and pasted the private key first, but
← PreviousNext →
Related archive views
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.