Part of the CustodyStress archive of observed Bitcoin custody incidents

Browse archive Archive statistics Scenarios Dependencies About

CS-00064

Wallet Encryption Without Post-Encryption Backup: 5 BTC Change Address Lost

Indeterminate

Wallet passphrase was unavailable — whether access was ultimately recovered is not known.

Case description

In December 2012, a BitcoinTalk user reported a custody failure involving wallet encryption and backup timing. The user had received 10 BTC across two transactions and maintained an unencrypted backup of their wallet.dat file. Weeks or months after creating this backup, the user encrypted their wallet with a passphrase but did not generate a new backup file afterward. The passphrase was subsequently forgotten, though the user retained partial memory of its composition.

When the user attempted to send 4 BTC from a 9 BTC input, the Bitcoin client consumed the entire input and generated a 5 BTC change output back to the wallet. This change address was derived from the post-encryption key pool and therefore did not exist in the pre-encryption backup file. Upon restoring the unencrypted backup, only the original 1 BTC test transaction appeared; the 5 BTC change output remained inaccessible.

Bitcoin Core's encryption mechanism (wallet.cpp NewKeyPool() function) deliberately discards the pre-encrypted address pool and generates a new one upon passphrase activation. This design prevents encrypted wallets from using unencrypted key material and forces any recovery attempt to rely on brute-force passphrase cracking. Community members confirmed this behavior matched source code design. At the time, 5 BTC had approximate value of £40–50 USD. The user characterized the loss as a matter of principle rather than significant financial harm and indicated willingness to pursue brute-force recovery with assistance from experienced community members (riX and Revalin), though no documented outcome of such recovery appears in the thread.

Custody context

Stress condition	Passphrase unavailable
Custody system	Software wallet
Outcome	Indeterminate
Documentation	Present and interpretable
Year observed	2012
Country	unknown

Structural dependencies observed

What this illustrates

The seed phrase was there, but the passphrase that unlocked it was gone. Both are required. A software wallet stores keys on the device — whether a phone or computer. When the device is lost or the application is uninstalled, access depends entirely on whether a seed phrase was recorded and stored independently. There was no documentation of how access worked. Without it, there was no path back in. An indeterminate outcome reflects the limits of available information. Whether anyone eventually gained access is not documented in the sources reviewed.

Why this matters

Why passphrases fail years after they are set

A passphrase adds a second layer of security to a Bitcoin wallet: the seed phrase opens one wallet; the seed phrase plus the passphrase opens a different one. This structure is effective at protecting against seed phrase theft. It is poorly designed for long-term memory reliability.

The failure mode documented consistently across observed cases is temporal: the passphrase is set with confidence, not used for an extended period, and then cannot be reproduced exactly when needed. A single character difference — different capitalization, an added space, a slightly different special character — produces a different wallet with a zero balance. The holder may be certain they remember the passphrase while being unable to produce the exact string that was originally set.

What makes this particularly difficult is that there is no signal at the moment of failure. A wrong passphrase does not produce an error message. It opens an empty wallet. The holder sees a zero balance and typically concludes the passphrase was wrong — but without knowing which part was wrong, or by how much.

Professional passphrase recovery services can attempt permutations when the holder has partial information: they remember the general structure, typical patterns they use for passwords, the approximate length, or that it included a specific word. Recovery from total non-recollection is not feasible.

How this category of failure is typically preventable

The preventive action is to store a passphrase record — not with the seed phrase, which would defeat its security purpose, but in a separate secure location accessible to the holder and potentially a designated recovery person. A passphrase that exists only in memory has a time horizon: it will eventually be forgotten, and the timing is unpredictable.

Frequently asked questions

Can a forgotten Bitcoin wallet passphrase be recovered?

In most cases, no. A wallet passphrase is not stored on the device, the network, or any recoverable system. It exists only in the holder's memory. If forgotten, there is no reset mechanism and no institution that can retrieve it. Some professional recovery services attempt passphrase variations for holders who remember partial information — but this is only feasible if the original passphrase had a recognizable pattern.

Is a Bitcoin passphrase the same as the seed phrase?

No. A passphrase is an additional secret layered on top of the seed phrase. The seed phrase alone generates one wallet; the seed phrase plus a specific passphrase generates a different wallet. Both are required for access. Losing the passphrase while retaining the seed phrase still blocks access — the seed alone will open an empty wallet, not the funded one.

Why do Bitcoin passphrases get forgotten even when the owner remembers setting one?

Passphrases are often set once during wallet setup and then not used again for months or years. Memory of infrequently used information degrades over time, and even small deviations — different capitalization, added space, slightly different word order — produce a completely different wallet with a zero balance. The holder may recall setting a passphrase clearly while being unable to reproduce the exact characters required.

Source

Publicly Reported

Evidence link

https://bitcointalk.org/index.php?topic=131619.0

Most structurally similar case

13.8 BTC Lost to Forgotten Wallet.dat Password: DIY and Professional Recovery Attempts

Passphrase unavailable · Software wallet · 2013 Indeterminate

This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case

← All cases

Framework references

Where Bitcoin Custody Intersects Legal and Fiduciary Authority

Where custody creates gaps in estate planning, fiduciary duty, and professional responsibility.

Professional Scope Boundary Matrix

What each professional or product covers, what they do not, and where gaps form between them.

The Independent Assessment Layer in Bitcoin Custody

How independent diagnostic layers emerge when multiple parties depend on shared infrastructure.

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:

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.
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.
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.