CustodyStress
Archive › Browse by dependency and custody › Time-Sensitive Sequencing — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Time-Sensitive SequencingSoftware wallet

Time-Sensitive Sequencing — Software wallet

Cases where mobile wallet recovery depended on completing steps in sequence within a time window, typically involving expiring authentication codes or platform-imposed deadlines.

3% of all Software wallet cases in the archive involve this structural dependency. The blocked rate among them is 56% — 13 points below the archive-wide blocked rate of 69%. The most common recovery path is seed phrase recovery.

Archive analysis — 14 cases
Outcomes
56% of determinate cases resulted in blocked access — 13 percentage points below the archive-wide average of 69%. 33% resulted in recovered access — above the archive average.
Documentation coverage
36% of cases have indeterminate outcomes — higher than the archive average of 43%.
Primary stress condition
36% of cases involve seed phrase unavailable. Device loss accounts for a further 36%.
Documentation
36% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Time distribution
Cases span 2010–2025. 36% occurred in 2022 or later.
Structural dependency
100% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
14 observed cases
Blocked
5 (36%)
Constrained
1 (7%)
Survived
3 (21%)
Indeterminate
5 (36%)
Pre-HD Bitcoin Core Wallet Lost in OS Upgrade: Backup Strategy Failure
Software wallet
Indeterminate 2025
In June 2025, a Bitcoin forum user reported a custody failure involving a Bitcoin Core wallet created circa 2014, during the era before hierarchical determinist
Oxford Armed Robbery: £1.1 Million Cryptocurrency Transferred Under Physical Duress
Software wallet
Blocked 2025
In November 2025, four armed men robbed a vehicle containing five occupants near Oxford, England. During the incident, one occupant was subjected to physical co
External Hard Drive Theft with Private Key Recovery Attempt
Software wallet
Indeterminate 2024
On May 26, 2024, a BitcoinTalk user (Niandertal@2024) reported the theft of an external hard drive containing a Bitcoin wallet file. The user had retained posse
Early Bitcoin Miner Seeks File Signature Recovery After Hard Drive Deletion
Software wallet
Indeterminate 2024
DVCMI776 mined a significant quantity of Bitcoin during the early Bitcoin era and stored the wallet files on a hard drive. The drive subsequently failed, initia
Russian Couple Forced to Transfer Bitcoin Under Armed Coercion — September 2022
Software wallet
Blocked 2022
In September 2022, a Russian couple experienced a custody failure driven by physical coercion rather than technical or administrative error. Six attackers ambus
Bitcoin Core Wallet Password Access Anomaly: Selective Failure Across Change Outputs
Software wallet
Indeterminate 2021
In early January 2021, a couple recovered a legacy hard drive containing a Bitcoin Core wallet with accumulated mining rewards and promotional Bitcoin distribut
Deleted Temporary Wallet Recovery via Private Key Forensic Extraction
Software wallet
Survived 2015
In September 2015, a Bitcoin user known as dooglus encountered a self-imposed custody failure during a transaction resend operation. After noticing an unconfirm
Payment Processor: Passphrase Lost on Damaged Flash Drive, 200+ BTC Addresses at Risk
Software wallet
Constrained 2014
In June 2014, an operator running a Bitcoin payment processing system discovered that the flash drive storing the passphrase to their wallet had been irreversib
Wallet.dat Recovery Failure After Premature Bitcoin-Qt Reinstall
Software wallet
Blocked 2013
In mid-2013, a Bitcoin user operating under the handle spoonbender encountered a custody access failure rooted in device loss and procedural error during recove
Wallet File Swap Causes Transaction Invisibility: Blockchain Index Desynchronization (2011)
Software wallet
Survived 2011
Michael_S was running Bitcoin client version 0.3.19 on Ubuntu Linux in May 2011 and sought to improve security by splitting his holdings across two wallet.dat f
2010 Bitcoin Wallet Deleted and Partially Recovered: Data Integrity Compromised by Subsequent Disk Writes
Software wallet
Indeterminate 2010
rok95 mined Bitcoin using CPU mining in 2010 during the network's earliest phase, when such activity was accessible to casual users with standard computing hard
Stone Man Loses 8,999 BTC to Unbacked Change Address After Live CD Shutdown
Software wallet
Blocked 2010
In August 2010, a BitcoinTalk user known as Stone Man purchased 9,000 BTC on an exchange and transferred them to a Bitcoin client running on a Debian Linux live
Copay Wallet Recovery Failed: Mnemonic Word Sequence Error
Software wallet
Blocked
In February 2020, a Copay wallet user posted to Bitcoin Stack Exchange reporting total loss of funds despite possessing a complete 12-word mnemonic backup. The
Android Smartphone Theft: Bitcoin Recovery via Archived Email Wallet Backup
Software wallet
Survived
An Android smartphone user experienced theft of an older device worth approximately $80. The phone contained a mobile wallet application with roughly $150 in Bi
Browse by dependency and custody
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.

Original text
Rate this translation
Your feedback will be used to help improve Google Translate