CustodyStress
Archive › Trigger categories › Passphrase Never Recorded
Part of the CustodyStress archive of observed Bitcoin custody incidents

Passphrase Never Recorded

Cases where a BIP39 passphrase was set during wallet creation but never written down or stored separately from the seed phrase. The passphrase was required to derive the correct extended keys.

passphrase never recorded cases have a 45% survival rate among determinate outcomes — one of the higher recovery rates in the archive. The most common recovery path is no path available.

Archive analysis — 37 cases
Outcomes
55% of determinate cases resulted in blocked access — 14 percentage points below the archive-wide average of 69%. 45% resulted in recovered access — above the archive average.
Documentation coverage
70% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
59% of cases involved software wallet, followed by exchange custody at 35%.
Primary stress condition
59% of cases involve passphrase unavailable. Seed phrase unavailable accounts for a further 27%.
Documentation
70% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
92% of cases carry a passphrase dependency dependency tag — the most common structural factor in this subset.
6
Blocked
0
Constrained
5
Survived
26
Indeterminate

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

37 observed cases
Blocked
6 (16%)
Survived
5 (14%)
Indeterminate
26 (70%)
Blockchain.com Wallet Inaccessible: Primary Password Works, Secondary Password Lost, Legacy Seed Incompatible
Exchange custody
Indeterminate 2024
In December 2024, a Bitcoin holder retrieved an encrypted wallet backup from Dropbox containing credentials for a Blockchain.info (now Blockchain.com) account o
Forgotten BIP39 Passphrase: BTCRecover Brute-Force Fails to Recover Access
Software wallet
Indeterminate 2024
JMASTERJ, a BitcoinTalk forum user, discovered a critical access failure in a self-custody wallet setup using a 12-word BIP39 seed phrase combined with an addit
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.
Trezor Passphrase Forgotten After Factory Reset — Successful Recovery via Community Support
Hardware wallet with passphrase
Survived 2024
BTCRSMD, a moderately experienced Bitcoin user, executed a deliberate custody strategy in July 2024. The user purchased Bitcoin via Swan and routed the coins th
180 BTC Lost Due to Forgotten Custom SHA256 Passphrase; Year-Long Manual Recovery Attempt
Software wallet
Indeterminate 2022
In January 2022, a BitcoinTalk user (k844738i) disclosed a critical custody failure spanning approximately one year. The user had created a Bitcoin wallet years
MultiBit Classic Wallet Password Lost, No Seed Phrase Documented (2014)
Software wallet
Indeterminate 2021
In January 2021, a user identified as mr_fish2021 recovered an old Windows computer containing a MultiBit Classic wallet created in 2014. The wallet held an und
Incomplete BIP39 Seed Recovery: 11 Words, Missing Documentation, Unknown Outcome
Software wallet
Indeterminate 2021
On January 9, 2021, BitcoinTalk user P.hanseens posted a technical support request describing inaccessible Bitcoin secured by a 12-word BIP39 seed phrase with o
Bitcoin Core Wallet Password Access Anomaly: Selective Failure Across Change Outputs
Software wallet
Indeterminate 2021
In early January 2021, a couple recovered a legacy hard drive containing a Bitcoin Core wallet with accumulated mining rewards and promotional Bitcoin distribut
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
Multibit Wallet Recovery Failure: Invalid 16-Word Seed Phrase After 7 Years
Software wallet
Indeterminate 2021
NickyGH established a Multibit wallet in 2014 at a Bitcoin education event held in Shoreditch, London. A technician guided the setup and instructed the user to
BIP38-Encrypted Paper Wallet: Forgotten Passphrase Blocks Access
Software wallet
Indeterminate 2021
On 12 January 2021, a Bitcoin user with the forum handle abashai posted to the BitcoinTalk Technical Support forum describing a custody access failure involving
BIP38 Passphrase Loss: Paper Wallet Rendered Inaccessible
Software wallet
Indeterminate 2021
In January 2021, a BitcoinTalk user (handle: abashai) discovered a critical custody access failure after generating a paper wallet with BIP38 encryption. The us
Five Old Blockchain.info Wallets Inaccessible: Non-Standard Recovery Phrases Beyond Recovery Tools
Exchange custody
Indeterminate 2020
In July 2020, forum user gbola reported discovering five old Blockchain.info recovery phrases originating from approximately 2014, when the user's family were e
Blockchain.com Wallet Locked: Partial Recovery Phrase and Lost Secondary Withdrawal Password
Exchange custody
Indeterminate 2020
In September 2020, a BitcoinTalk user identified as sa14 reported complete inability to access a Blockchain.com wallet created on November 29, 2017, despite pos
Electrum Seed Phrase Mismatch: Valid Addresses, Missing Funds
Software wallet
Indeterminate 2018
In January 2018, forum user 'thenarog' encountered a nuanced custody failure involving an Electrum desktop wallet. The user held a wallet.dat backup file protec
Paper Wallet QR Code Case Mismatch: Single Character Locked Access for 2.5 Years
Software wallet
Survived 2018
Al Reno generated an offline paper wallet using bitaddress.org in August 2018, manually printing both public and private keys with QR codes to physical paper. H
4 BTC Inaccessible in BIP38-Encrypted Paper Wallet After Passphrase Loss
Software wallet
Indeterminate 2018
In February 2018, a Bitcoin holder discovered that access to 4 BTC distributed across three BIP38-encrypted paper wallet addresses had become impossible due to
Lost Final Word of Ledger Nano S 24-Word Seed: 110,000 Dogecoin Case
Hardware wallet (single key)
Indeterminate 2018
On March 8, 2018, a BitcoinTalk forum user identified as Ma1k reported losing the 24th word of a Ledger Nano S BIP39 recovery seed phrase. The loss occurred aft
Blockchain.info Watch-Only Import Without Private Key Retention
Exchange custody
Blocked 2017
In June 2017, a Bitcoin Talk forum user (amirheavy666) discovered that approximately 0.00027375 BTC accumulated on a Blockchain.info wallet created around 2014
Institutional lockout — exchange custody (2017)
Exchange custody
Indeterminate 2017
Between 2014 and 2015, the user created cryptocurrency accounts on blockchain.info and retained the mnemonic seed phrases. By December 2017, the user attempted
Hive Wallet Litecoin Loss: 12-Word Seed Phrase Never Documented
Software wallet
Indeterminate 2017
PentagonPinnacle purchased litecoins several years before May 2017 and installed them in a Hive Wallet application on an iPad. At the time of wallet creation, t
Blockchain.info Account Lockout: Forgotten Password and Missing Recovery Phrase (2013 Wallet)
Exchange custody
Indeterminate 2017
A BitcoinTalk forum user identified as MARK 888 reported in October 2017 that they had lost access to a Blockchain.info wallet created around 2013. The user ret
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
Teenager Locked Out of Blockchain.info Wallet After Password Change – No Seed Backup
Exchange custody
Indeterminate 2017
In late October 2017, a Russian Bitcoin user (forum username: see123123) discovered they could no longer access their Blockchain.info hosted wallet. The user ha
BIP38 Paper Wallet Passphrase Lost — 0.7 BTC Inaccessible (2020)
Software wallet
Indeterminate 2017
A BitcoinTalk user (arkaraj) purchased approximately 0.7 BTC in 2017 and generated a paper wallet using bitaddress.org with BIP38 passphrase encryption. The use
← PreviousNext →
Trigger categories
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