CustodyStress
Archive › Browse by outcome and stress › Blocked — Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
BlockedPassphrase unavailable

Blocked — Passphrase unavailable

Cases where a wallet became permanently inaccessible because the passphrase was unavailable. A passphrase-protected wallet without the passphrase is cryptographically unrecoverable — the seed phrase alone is insufficient.

52% of all passphrase-unavailable cases in the archive result in a blocked outcome. These 46 cases represent the full 52% — the subset where this specific combination of stress condition and outcome is documented. The most common recovery path is estate process.

Archive analysis — 46 cases
Outcomes
100% of determinate cases resulted in blocked access — 31 percentage points above the archive-wide average of 69%. Only 0% resulted in recovered access — one of the lower survival rates in the archive.
Custody type
61% of cases involved software wallet, followed by exchange custody at 20%.
Documentation
33% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Structural dependency
93% of cases carry a passphrase dependency dependency tag — the most common structural factor in this subset.
46
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

46 observed cases
Blocked
46 (100%)
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
Inherited Bitcoin Core Wallet with Forgotten Passphrase: No Technical Recovery
Software wallet
Blocked 2025
In May 2025, a user posted to Bitcoin Stack Exchange describing an inheritance custody failure: their father created a Bitcoin Core wallet years prior and then
50–100 Bitcoin Lost on Old Hard Drive Due to Missing Passphrase
Software wallet
Blocked 2024
In December 2024, a professional contacted Stack Exchange reporting that a colleague possessed 50–100 bitcoins stored on an old hard drive in a bitcoin-qt walle
Legacy Blockchain.com Wallet Inaccessible: Private Keys Don't Match Funded Address
Exchange custody
Blocked 2022
In November 2022, a user (Gemwolf) discovered an old hard drive containing a wallet.dat file and notes from his 2012 Bitcoin experimentation period. Mining acti
150 BTC Passphrase Lost — No Recovery Method Available
Software wallet
Blocked 2022
On August 19, 2022, a user posted to Bitcoin Stack Exchange describing loss of access to a Bitcoin Core wallet containing 150 BTC (valued at approximately €3.2
Bitcoin Core Wallet: Encryption Mismatch Between Old Wallet Format and Modern Change Addresses
Software wallet
Blocked 2021
In early January 2021, a husband and wife discovered an old hard drive containing a Bitcoin Core wallet from prior mining operations and promotional credits. On
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
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
Dash Core Wallet Passphrase Forgotten: Permanent Access Loss
Software wallet
Blocked 2017
In April 2017, a BitcoinTalk forum user identified as 'Ramchandra' posted describing a custody failure involving a Dash Core software wallet. The user had encry
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
Blockchain.info Wallet Lockout: Documented Seed Phrase Fails Validation
Exchange custody
Blocked 2017
Sir11k created a Blockchain.info custodial wallet in June 2017 with approximately €20 worth of Bitcoin. Upon account creation, the platform provided a 12-word B
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
Blockchain.info Wallet: Lost Password and Recovery Phrase on Phone
Exchange custody
Blocked 2017
In June 2017, a Blockchain.info user posted on Bitcoin Stack Exchange reporting the loss of both their wallet password and 12-word recovery phrase after losing
Wallet File Corruption After Windows Reinstall: Litecoin Locked Despite Correct Passphrase
Software wallet
Blocked 2017
SnowRoll purchased Litecoin on a Windows 10 desktop in April 2017, encrypting the wallet with a self-selected passphrase. After two transactions, the user encou
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,
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
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
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
Encrypted Bitcoin Core Wallet Loss: Forgotten Passphrase, Selective Key Export Failure
Software wallet
Blocked 2015
In October 2015, forum user phantitox reported recovering a wallet.dat file from a damaged hard drive, only to discover the passphrase protecting the encrypted
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
0.3 BTC Lost After Uninstalling Blockchain.info Desktop Wallet Without Backup
Exchange custody
Blocked 2015
In June 2015, a user identified as Williams2017 received approximately 0.3 BTC (then valued at roughly $70 USD) from an entity called 'www.instantgold.ng' to th
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
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
Brad Yasar: Desktop-Mined Bitcoin Locked by Forgotten Passwords
Software wallet
Blocked 2012
Brad Yasar, a Los Angeles-based entrepreneur, mined Bitcoin on multiple desktop computers during the network's earliest years when mining was accessible to indi
← PreviousNext →
Browse by outcome and stress
Related pages
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.