CustodyStress
Archive › Browse by trigger and stress condition › Passphrase Unavailable — Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
Passphrase_unavailablePassphrase unavailable

Passphrase Unavailable — Passphrase unavailable

Bitcoin custody cases involving passphrase unavailable and passphrase unavailable.

15 cases in this intersection. 83% of determinate cases resulted in a blocked outcome and 17% in access survived. The most common recovery path is password bruteforce.

Archive analysis — 15 cases
Outcomes
83% of determinate cases resulted in blocked access — 14 percentage points above the archive-wide average of 69%.
Documentation coverage
60% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
80% of cases involved software wallet, followed by hardware wallet with passphrase at 13%.
Recovery path
Password Bruteforce is the most documented recovery path (8 cases, 53% of subset).
Documentation
87% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
93% of cases carry a passphrase dependency dependency tag — the most common structural factor in this subset.
15 observed cases
Blocked
5 (33%)
Survived
1 (7%)
Indeterminate
9 (60%)
Trezor Model T Passphrase Loss: 0.7175 BTC On-Chain, Inaccessible
Hardware wallet with passphrase
Blocked 2025
In late December 2025, jwsutherland transferred approximately 0.7175 BTC from the Canadian exchange Newton to a native SegWit (bech32) address generated by a Tr
Lost Bitcoin Core Wallet from 2011: Unknown Encryption, No Private Key Access
Software wallet
Indeterminate 2023
In October 2023, a BitcoinTalk forum user identified as Borislee posted a request for assistance accessing an old Bitcoin Core wallet dating to approximately 20
AES256-CBC Encrypted Wallet: Partial Password Loss and Brute-Force Recovery
Software wallet
Indeterminate 2022
In July 2022, a Bitcoin holder posted to Stack Exchange describing an AES256-CBC encrypted wallet protected by a 15-character passphrase combining uppercase, lo
Bitcoin Core 0.21 Wallet Rejects Passphrase During Spend Attempt
Software wallet
Indeterminate 2021
In April 2021, a Bitcoin Core 0.21 user encountered a critical custody failure when attempting to send coins from an encrypted wallet. The wallet prompted for a
Bitcoin Core Wallet Passphrase Rejected: $400 USD Inaccessible
Software wallet
Blocked 2018
In September 2018, a Bitcoin Core user reported being locked out of their encrypted software wallet containing approximately $400 USD in Bitcoin. The wallet had
Blockchain.info Wallet Password Lost, No Seed Backup: Recovery Blocked
Exchange custody
Indeterminate 2018
In July 2018, a Bitcoin holder transferred funds to his wife's blockchain.info mobile wallet during a phone transition. The wife subsequently forgot the wallet
MultiBit Classic Password Rejection: Verified Credentials, Inaccessible Funds
Software wallet
Blocked 2017
In November 2017, a BitcoinTalk user reported a critical wallet access failure involving MultiBit Classic 0.5.15 on macOS. The user had created two encrypted wa
MultiBit Wallet Password Forgotten: Encrypted Backup Available but Inaccessible
Software wallet
Indeterminate 2017
On December 30, 2017, a Bitcoin holder posted to Stack Exchange describing a custody failure involving MultiBit, a desktop software wallet popular during the mi
Bitcoin Core Wallet Password Not Recognized After Encryption and Crash
Software wallet
Indeterminate 2017
In February 2017, a Bitcoin Core user encrypted their wallet using a 5-digit password they used on another application. During the encryption process, the softw
10 Million Dogecoins Inaccessible After Forgotten Spending PIN on Android Wallet
Software wallet
Blocked 2016
In January 2016, a user accumulated approximately 10 million Dogecoins (valued at roughly $1,500 USD) on an Android Langerhans wallet over one week. The coins w
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
Lost Passphrase to Ledger BIP39 Hidden Wallet—Seed Phrase Insufficient
Hardware wallet with passphrase
Indeterminate
A Bitcoin holder with existing experience in cryptocurrency set up an advanced feature on their Ledger hardware wallet known as BIP39 passphrase protection. Thi
Recovering Encrypted MultiBit Private Key When Decryption Method Is Forgotten
Software wallet
Survived
In April 2021, a Bitcoin holder sought recovery of a private key they had exported from MultiBit Classic years earlier. The key had been written to a text file
Wallet Passphrase Rejected Despite Correct Entry: Bitcoin Custody Failure
Software wallet
Indeterminate
In June 2019, a Bitcoin Core user reported that their wallet passphrase was not being accepted during an attempted transaction, despite having written it down c
BIP38-Encrypted Paper Wallet: Permanent Loss After Forgotten Passphrase
Software wallet
Blocked
In December 2017, a new Bitcoin user created a paper wallet using BitAddress.org and elected to encrypt it with BIP38 (Bitcoin Improvement Proposal 38), a stand
Browse by trigger and stress condition
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