Part of the CustodyStress archive of observed Bitcoin custody incidents

Browse archive Archive statistics Scenarios Dependencies About

CS-00058

Formatted Computer, Lost Wallet.dat Access—Recovered via Time Machine Backup

Survived

No documentation described the custody setup — but a recovery path was eventually found.

Case description

On July 3, 2011, forum user Omega0255 reported a critical custody error with a 1 BTC mining pool payment. The user had formatted their SSD drive using a secure 5-pass erase method before installing macOS 10.7 Lion, intending to permanently destroy the associated wallet.dat file. However, immediately after the erase, a payment of 1 BTC arrived at an address that had been linked to that now-deleted wallet. The user initially accepted the loss as permanent, given the strength of the secure erase standard used.

In early 2011, this seemed reasonable: a proper cryptographic erase should render file recovery tools ineffective. The user contacted the forum seeking confirmation that recovery was impossible. However, during discussion with community members including Alex Beckenham and Stephen Gornick (a Legendary-status forum contributor), Omega0255 recalled maintaining a Time Machine backup—macOS's automated continuous backup system—that predated the format operation.

Gornick provided detailed technical guidance on wallet.dat structure and recovery methodology. The wallet.dat file contains the private keys necessary to spend Bitcoin received to addresses generated from that wallet. Gornick outlined two recovery paths: direct restoration of the old wallet if no subsequent wallet activity had occurred, or a staged recovery using an intermediate address if a new wallet had been created in the interim.

The root cause was knowledge concentration: the user possessed the necessary backup but did not maintain active, conscious awareness of its existence until prompted by community discussion. At July 2011 exchange rates ($15–16 USD per BTC), the asset value was approximately $15–16, though the precedent value was significant for early Bitcoin custody documentation. The resolution highlighted the utility of automated backup systems in offsetting human memory lapses and the importance of the 3-2-1 backup principle, which gained visibility in Bitcoin circles through this case.

Custody context

Stress condition	Documentation absent
Custody system	Software wallet
Outcome	Survived
Documentation	Present and interpretable
Year observed	2011
Country	United States

Structural dependencies observed

Device Specific Access Undocumented procedure

Why this matters

What the absence of documentation actually removes

Documentation absent cases are the most evenly distributed across custody types in this archive. The absence of documentation is not a function of how sophisticated the setup was — it is a function of whether the owner thought about anyone else ever needing to use it.

What documentation provides is a starting point. Without it, heirs face three unknowns before they face any access problem: does the Bitcoin exist, where is it held, and what is needed to access it. Most of this information cannot be reconstructed after the owner dies or becomes incapacitated. Educated guesses, blockchain searches, and device inventories occasionally locate wallets — but without credentials, finding the wallet does not help.

Cases in this archive where documentation was absent but recovery succeeded typically involved one of two factors: an exchange account where the heir knew the email address and could navigate the account recovery process, or a designated person who had been given credentials informally and could act. Self-custody without any documentation or designated knowledge-holder is consistently the worst combination.

The content of documentation matters as much as its existence. A note that says "my Bitcoin is in a hardware wallet in the safe" is better than nothing but insufficient. Effective documentation specifies: what type of wallet, where the seed phrase is stored, whether a passphrase exists and where it is documented, and any exchange accounts and the email addresses used. It should be tested — the executor should be able to confirm the information is accurate before it is needed.

How this category of failure is typically preventable

Documentation does not need to expose credentials to be useful. A document that describes the custody structure, points to where credentials are stored, and names a person who has been briefed can be stored without security risk. The goal is not to put the seed phrase in a filing cabinet — it is to ensure the executor has a map, not a blank wall.

Read more: Instruction Trust Failure →

Frequently asked questions

What happens to Bitcoin if there are no written instructions for heirs?

Without documentation, heirs face a search problem before they face an access problem. They must first determine whether Bitcoin exists, then which wallet holds it, then where the credentials are stored, then how to use them. Most of this information dies with the owner. Cases without documentation consistently produce the worst outcomes in the archive — not because recovery is impossible, but because heirs have no starting point.

What information should be documented for Bitcoin inheritance?

At minimum: confirmation that Bitcoin exists and its approximate value, the type of custody arrangement used, where the seed phrase is stored, whether a passphrase was set, and contact information for any exchange accounts. A designated person should know this documentation exists and where to find it. Ideally it should be testable — the executor should be able to confirm the information is correct before the owner dies.

Can Bitcoin inheritance documentation be stored with a will?

It can, but with caution. A will becomes a public document when probated. Seed phrases or passphrase hints stored in a will become accessible to anyone who views the probate record. Sensitive access information is typically better stored separately, with the will or estate documents only noting that Bitcoin exists and directing executors to where the documentation is held.

Source

Publicly Reported

Evidence link

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

Most structurally similar case

Bomben Recovers 2013 Bitcoin Wallet Locked by Nonstandard Private Key Encoding

Documentation absent · Software wallet · 2013 Survived

Related cases

Structural patterns in this case

Device discarded

33 cases involve documentation absent 455 cases involve software wallet View archive statistics →

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.