CustodyStress
Archive › Browse by documentation and stress › Present and Interpretable — Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
Present And InterpretablePassphrase unavailable

Present and Interpretable — Passphrase unavailable

Cases where documentation was present and interpretable but a passphrase failure still blocked access. These cases reveal a documentation gap: the written record did not include the passphrase, or the passphrase record was not accessible.

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

Archive analysis — 38 cases
Outcomes
44% of determinate cases resulted in blocked access — 25 percentage points below the archive-wide average of 69%. 47% resulted in recovered access — above the archive average.
Custody type
66% of cases involved software wallet, followed by hardware wallet (single key) at 13%.
Recovery path
Password Bruteforce is the most documented recovery path (11 cases, 29% of subset). Of those with a determinate outcome, 100% resulted in recovered or constrained access.
Documentation
100% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Time distribution
Cases span 2009–2024. Only 3% occurred in 2022 or later — concentrated in earlier periods.
Structural dependency
95% of cases carry a passphrase dependency dependency tag — the most common structural factor in this subset.
15
Blocked
3
Constrained
16
Survived
4
Indeterminate

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

38 observed cases
Blocked
15 (39%)
Constrained
3 (8%)
Survived
16 (42%)
Indeterminate
4 (11%)
Samourai Wallet Seizure: Recovering Bitcoin After Platform Shutdown
Software wallet
Survived 2024
On April 28, 2024, a BitcoinTalk user reported that Bitcoin deposited to their Samourai Wallet became inaccessible following the FBI's shutdown of the platform.
Armory v0.88.1 Desktop Wallet: 50+ BTC Inaccessible Due to Forgotten Passphrase
Software wallet
Indeterminate 2021
In April 2021, a BitcoinTalk user identified as vect0rz reported losing access to an Armory v0.88.1 desktop wallet containing over 50 BTC. The wallet was create
Blocktrail Wallet Recovery: Lost Password, Multiple Backup Seeds, Platform Tool Failure
Exchange custody
Constrained 2021
LSU777, a BitcoinTalk forum user, attempted recovery of a Blocktrail-hosted wallet created in the pre-fork era (circa 2016) after losing the primary password. T
250 LTC Custody Failure: Lost Passphrase, No Recovery Path
Software wallet
Indeterminate 2021
In January 2021, a BitcoinTalk forum user identified as realman123 disclosed a custody failure involving approximately 250 Litecoin stored in a Litecoin Core de
Forgotten 115-Character Wallet Password Recovered via GPU Typo-Bruteforce
Software wallet
Survived 2019
In August 2017, a Bitcoin enthusiast created a Bitcoin Core wallet secured by a 115-character sentence-based password and wrote it down. In June 2019, when they
Passphrase unavailable — exchange custody, unknown (2019)
Exchange custody
Blocked 2019
A 2019 BitcoinTalk thread documented a recurring custody failure pattern affecting blockchain.com (formerly blockchain.info) users from the 2011–2014 era. The o
Electrum Seed Version 18 Password Recovery: btcrecover Incompatibility Resolved
Software wallet
Survived 2019
In December 2019, a BitcoinTalk user (red14159) discovered a wallet.dat file from an Electrum wallet they had lost access to approximately three years earlier.
Alexander Halavais: Forgotten Password on 2010 Experimental Bitcoin Purchase
Software wallet
Blocked 2017
Alexander Halavais, an Associate Professor in the School of Social and Behavioral Sciences at Arizona State University, purchased a small quantity of Bitcoin ar
Forgot Trezor PIN and Seed Words: $30,000 Bitcoin Recovery
Hardware wallet (single key)
Survived 2017
In 2017, during Bitcoin's price surge, a user documented their experience losing access to a Trezor hardware wallet containing approximately $30,000 in Bitcoin.
Forgotten Trezor PIN and Lost Seed Words: $30,000 Bitcoin Recovery
Hardware wallet (single key)
Survived 2017
In 2017, a Bitcoin holder using a Trezor hardware wallet lost access to approximately $30,000 worth of Bitcoin after forgetting both the device PIN and the back
Trezor PIN and Seed Words Forgotten: $30,000 Bitcoin Recovery
Hardware wallet (single key)
Survived 2017
In October 2017, a Trezor hardware wallet user discovered they had forgotten both their PIN and recovery seed words, creating a dual-layer access barrier to app
Hidden Line Feed Character Blocks Bitcoin Core Wallet Access
Software wallet
Survived 2017
In February 2017, scutzi128 documented a Bitcoin Core wallet access failure on the Bitcoin Technical Support forum. The user had encrypted their wallet with a 2
33.54 BTC Corrupted in Wallet.dat: Binary File Opened in Text Editor
Software wallet
Blocked 2017
In July 2016 or earlier, ketubi saved a wallet.dat file from Bitcoin Core to a USB drive, intending to create an offline backup. Years later, in December 2017,
Kevin Durant Locked Out of Coinbase Bitcoin Account for 9 Years After 2016 Purchase
Exchange custody
Constrained 2016
Kevin Durant purchased Bitcoin on Coinbase in September 2016 at approximately $650 per coin, following repeated conversations with Golden State Warriors teammat
Electrum Wallet Password Loss: 4 BTC Inaccessible Without Seed Backup
Software wallet
Blocked 2016
On April 6, 2016, Andi300 posted on forum.bitcoin.com describing an immediate custody failure: the user had just received 4 BTC but was unable to send or access
Andreas1324 Permanently Locked Out of Electrum Wallet: Forgotten Password, No Seed Backup (May 2016)
Software wallet
Blocked 2016
In May 2016, a BitcoinTalk user posting as Andreas1324 opened a public thread in the Electrum wallet subforum describing complete loss of access to a wallet hol
BIP39 Passphrase Confusion: How a Mobile PIN Hid Bitcoin for Five Years
Software wallet
Survived 2016
In mid-2016, the user's Android device failed. They recovered their MyCelium wallet using their seed phrase but found all pre-2016 Bitcoin gone. The wallet show
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
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
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
Forgotten Passphrase and Overwritten Wallet.dat: 0.50 BTC Permanently Lost
Software wallet
Blocked 2015
In May 2015, BitcoinTalk user grovearmada discovered they had lost access to an encrypted Bitcoin wallet containing 0.50 BTC (approximately $115–120 USD at 2015
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.
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
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
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
← PreviousNext →
Browse by documentation 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.