CustodyStress
Archive › Browse by dependency and outcome › Single-Person Knowledge — Blocked
Part of the CustodyStress archive of observed Bitcoin custody incidents
Single-Person KnowledgeBlocked

Single-Person Knowledge — Blocked

Cases where single-person knowledge concentration produced a blocked outcome. When the one person who knew the custody procedure became unavailable, no recovery path existed. This is the most common structural predictor of blocked outcomes in the archive.

245 cases in this intersection. 100% of determinate cases resulted in a blocked outcome. The most common recovery path is no path available.

245
Blocked
0
Constrained
0
Survived
0
Indeterminate

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

245 observed cases
Blocked
245 (100%)
Lost Bitcoin from 2011 Dialcoin Purchase — Wallet Unknown, Documentation Discarded
Unknown custody system
Blocked 2011
In May 2017, a Bitcoin Stack Exchange user identified as David posted about bitcoins purchased in 2011 from Dialcoin, a now-defunct early exchange platform. Dav
26 BTC Lost: Developer Formats Drive Containing Wallet, Gives to Mother-in-Law
Software wallet
Blocked 2011
In October 2021, a Hacker News user identified as jakewins disclosed a significant custody failure from the early Bitcoin era. The user possessed 26 BTC stored
MyBitcoin.com Custody Collapse (July 2011): 78,747 BTC Lost, Partial Refund, Operator Never Identified
Exchange custody
Blocked 2011
MyBitcoin.com, launched in 2010, became one of the first popular custodial Bitcoin web wallet services at a time when hardware wallets did not exist and self-cu
Brad Yasar: Early Miner Locks Out Thousands of BTC Across Multiple Drives
Software wallet
Blocked 2011
Brad Yasar, a Los Angeles-based entrepreneur, mined thousands of Bitcoin on several desktop computers during the earliest years of the network when solo mining
Lost Bitcoin Mining Wallet on Decommissioned PC: Data Overwritten Beyond Recovery
Software wallet
Blocked 2010
In 2009 or 2010, rosnick92 and his father mined Bitcoin on a personal computer for several days, earning what he recalls as 'a few pennies per day'—an amount he
Seed unavailable — software wallet (2010)
Software wallet
Blocked 2010
On July 14, 2010, a BitcoinTalk user with the handle ksd5 reported a critical loss in a forum thread posted just two days after account creation. The user held
2,700 BTC Lost to Antivirus Deletion and Unverified Drive Format
Software wallet
Blocked 2010
An individual received a hard drive containing a wallet.dat file—allegedly holding approximately 2,700 BTC—sent by an early Bitcoin adopter around 2010 via emai
9,000 BTC Lost to Unrebacked Change Address: Early Bitcoin Wallet Flaw (2010)
Software wallet
Blocked 2010
In August 2010, a Bitcoin user purchased 9,000 BTC and conducted a single test transaction: sending 1 BTC to his own address to confirm network functionality. T
8,999 BTC Lost to Non-Deterministic Wallet Change Address Design
Software wallet
Blocked 2010
In 2010, a Bitcoin user held approximately 9,000 BTC in a Bitcoin Core wallet. To validate his backup and recovery procedure, he executed a test transaction to
10,000 Bitcoin Lost When Laptop Discarded as Junk (2010)
Software wallet
Blocked 2010
In March or April 2010, while a final-year student at St. John's University in New York, an individual purchased 10,000 BTC from a local seller for approximatel
1,000 BTC Lost to Repeated Hard Drive Formatting: Self-Custody Without Backup
Software wallet
Blocked 2009
In January 2017, a BitcoinTalk forum user identified as myBitcoin2009 posted a recovery request describing a custody loss rooted in the earliest era of Bitcoin
3,000 BTC Locked on Discontinued Blockchain.com Wallet: Missing Email Address Blocks Recovery
Exchange custody
Blocked 2009
Ice22 acquired 3,000 BTC in June 2009 through an intermediary claiming to represent a Swiss or Swedish Bitcoin promotion entity. The acquisition process include
Multibit Desktop Wallet: Bitcoin Inaccessible After Platform Closure and File Loss
Software wallet
Blocked
A professional received a Bitcoin payment to an address generated by Multibit, a lightweight desktop wallet widely used during the early-to-mid 2010s. At the ti
7500 BTC Permanently Locked on IronKey Device After Passphrase Loss
Hardware wallet with passphrase
Blocked
A British engineer encrypted approximately 7500 BTC on an IronKey device, a third-party encrypted storage solution designed with progressive lockout mechanisms
Tax Conviction Forces $124M Bitcoin Disclosure Order, But Keys Remain Inaccessible
Hardware wallet (single key)
Blocked
Richard Ahlgren III, an early Bitcoin investor, was convicted of tax evasion for underreporting capital gains from cryptocurrency sales. A Texas federal court i
2.3 Bitcoin Inaccessible on Ledger Nano S: Owner Incapacity and Undocumented Credentials
Hardware wallet (single key)
Blocked
In 2019, one partner in a 16-year relationship created a Ledger Nano S hardware wallet and transferred 2.3 Bitcoin to it. The partner deliberately withheld both
Desktop Software Wallet Erased During PC Reset — Seed Phrase Never Recorded
Software wallet
Blocked
A Bitcoin holder maintained their first cryptocurrency wallet as a hot wallet on a personal computer, following a common early-adoption pattern of minimal secur
Stefan Thomas: 7,200 Bitcoin Inaccessible Behind IronKey Passphrase
Hardware wallet with passphrase
Blocked
Stefan Thomas, former Chief Technology Officer of Ripple, stored 7,200 BTC on an IronKey encrypted hard drive. The drive implemented a deliberate security const
50 BTC Lost After Accidental Hard Drive Format
Software wallet
Blocked
A Bitcoin holder maintained a wallet file on a hard drive without maintaining a backup. The drive was formatted, destroying the wallet data, before the loss was
James Howells' 7,500 Bitcoin: Hard Drive Lost in Newport Landfill
Software wallet
Blocked
James Howells, a software engineer in Newport, South Wales, accidentally discarded a hard drive containing approximately 7,500 to 8,000 Bitcoin in the early 201
100 Bitcoin Lost on Discarded Flash Drive: Permanent Access Failure
Software wallet
Blocked
During Bitcoin's early adoption phase, when the asset had negligible market value and was treated primarily as an experimental hobby, the original poster create
100 Bitcoin Lost to Discarded Flash Drive Without Backup
Software wallet
Blocked
An early Bitcoin adopter stored approximately 100 bitcoins on a flash drive during Bitcoin's formative years, likely before 2013, when the asset carried minimal
When Bitcoin Seed Phrases Are Lost at Death: Community Debate on Permanent Custody Failure
Hardware wallet (single key)
Blocked
A Reddit discussion explored a recurring custody failure scenario: an individual holds Bitcoin in self-custody using only a seed phrase known solely to them, wi
Executor Locked Out: Blockchain.com Wallet After Probate, Email Account Dead
Exchange custody
Blocked
A man's father passed away, leaving behind login credentials and a Bitcoin address recorded in estate documentation. During the multi-year probate process—compl
Inputs.io Security Breach and Platform Collapse — 4,100 BTC Lost
Exchange custody
Blocked
Inputs.io operated as a hosted web wallet service in the early Bitcoin era, when best practices for key management were still crystallizing. The platform genera
← PreviousNext →
Browse by dependency and outcome
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