CustodyStress
Archive › Browse by trigger and era › Forgotten Passphrase — Early Bitcoin (2009–2013)
Part of the CustodyStress archive of observed Bitcoin custody incidents
Forgotten_passphraseEarly Bitcoin

Forgotten Passphrase — Early Bitcoin (2009–2013)

Bitcoin custody cases involving forgotten passphrase and early bitcoin (2009–2013).

33 cases in this intersection. 36% of determinate cases resulted in a blocked outcome and 55% in access survived. The most common recovery path is password bruteforce.

Archive analysis — 33 cases
Outcomes
36% of determinate cases resulted in blocked access — 33 percentage points below the archive-wide average of 69%. 55% resulted in recovered access — above the archive average.
Documentation coverage
67% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
91% of cases involved software wallet, followed by exchange custody at 6%.
Primary stress condition
97% of cases involve passphrase unavailable. Documentation absent accounts for a further 3%.
Recovery path
Password Bruteforce is the most documented recovery path (24 cases, 73% of subset). Of those with a determinate outcome, 83% resulted in recovered or constrained access.
Documentation
73% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
4
Blocked
1
Constrained
6
Survived
22
Indeterminate

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

33 observed cases
Blocked
4 (12%)
Constrained
1 (3%)
Survived
6 (18%)
Indeterminate
22 (67%)
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
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
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
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
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
Bomben Recovers 2013 Bitcoin Wallet Locked by Nonstandard Private Key Encoding
Software wallet
Survived 2013
Bomben created a Bitcoin wallet in 2013 using software that implemented a nonstandard encoding for private keys, diverging from the Wallet Import Format (WIF) s
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-
Forgotten Passphrase Locks Desktop Wallet for 8 Years; btcrecover Enables Recovery
Software wallet
Survived 2013
In 2013, this individual created a Bitcoin wallet using desktop software, securing it with a passphrase. The holder subsequently lost memory of that passphrase
Blockchain.info Hosted Wallet Recovery: Password Reset via Seed Phrase (2013)
Exchange custody
Survived 2013
PandaNL opened a Blockchain.info hosted wallet in 2013 and over several years forgot the account password. The user retained three critical pieces of recovery i
BitcoinTalk User syuyu Locked Out of Wallet With ~32-Character Passphrase (January 2014)
Software wallet
Indeterminate 2013
In January 2014, a BitcoinTalk user known as 'syuyu' posted in an encrypted wallet recovery thread describing a locked software wallet they could no longer acce
1990 BTC Forgotten Passphrase: Pakistani Investor's Failed Recovery Attempts (2013)
Software wallet
Indeterminate 2013
In November 2013, a BitcoinTalk forum user identified as 'Britman' disclosed a significant custody failure affecting 1990 BTC accumulated throughout 2012 at pri
Blockchain.info 2013–2014 Wallet Access Failure: Encrypted Files, Lost Password, Functional Recovery Phrase
Exchange custody
Indeterminate 2013
User 'marvin42' created Bitcoin wallets via blockchain.info in 2013 or 2014 and retained two AES-encrypted backup files dated 28 February 2014 and 22 April 2013
Rahazan Develops and Shares PowerShell Wallet Recovery Script (2013)
Software wallet
Indeterminate 2013
In 2013, a BitcoinTalk user identifying as Rahazan faced a common early custody problem: an encrypted Bitcoin-Qt wallet with a forgotten passphrase. Rather than
BitcoinTalk User kentt Recovers Encrypted Wallet via Community Brute-Force Script (June 2013)
Software wallet
Survived 2013
In June 2013, BitcoinTalk user kentt posted confirmation of a successful wallet recovery using community-developed brute-force scripts circulated in topic 85495
SP4RK7 Locked Out of Protoshares Wallet: Single-Character Password Error, Recovery Bounty Offered
Software wallet
Indeterminate 2013
On November 30, 2013, BitcoinTalk user SP4RK7 posted in the encrypted wallet recovery thread describing a Protoshares wallet locked with encryption that appeare
BitcoinTalk User ez1btc: Encryption Password Transcription Error Blocks Large Bitcoin Wallet
Software wallet
Indeterminate 2012
In the encrypted wallet recovery thread on BitcoinTalk, user 'ez1btc' documented a custody failure rooted in transcription error rather than forgetfulness. At t
← PreviousNext →
Browse by trigger and era
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