CustodyStress
Archive › Structural dependencies › Time-Sensitive Sequencing
Part of the CustodyStress archive of observed Bitcoin custody incidents

Time-Sensitive Sequencing

Cases where recovery required completing steps in a specific sequence within a time window that could not be met.

36% of determinate cases in this category resulted in a blocked outcome. The most common recovery path is exchange support.

Archive analysis — 31 cases
Outcomes
36% of determinate cases resulted in blocked access — 33 percentage points below the archive-wide average of 69%. 50% resulted in constrained recovery.
Custody type
52% of cases involved exchange custody, followed by software wallet at 45%.
Primary stress condition
39% of cases involve vendor lockout. Seed phrase unavailable accounts for a further 19%.
Documentation
58% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
19% of cases involved large or very large holdings (10+ BTC).
8
Blocked
11
Constrained
3
Survived
9
Indeterminate

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

31 observed cases
Blocked
8 (26%)
Constrained
11 (35%)
Survived
3 (10%)
Indeterminate
9 (29%)
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
Sallanches Kidnapping: Retired Couple Extorted for €8 Million Cryptocurrency
Unknown custody system
Blocked 2025
In late December 2025, a retired couple residing in Sallanches, Haute-Savoie, France became the target of a kidnapping orchestrated by criminals seeking €8 mill
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
BTC.com Wallet Service Shutdown and Recovery Tool Failure
Exchange custody
Indeterminate 2022
In February 2022, BTC.com announced the shutdown of its wallet service, setting an April 1, 2022 deadline for users to withdraw funds. The announcement prompted
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
Cryptopia Exchange Hack and Liquidation: 960,000 Frozen Accounts, $400M Distributed Over 5 Years
Exchange custody
Constrained 2019
Cryptopia, a Christchurch-based cryptocurrency exchange serving 1.4 million registered users across approximately 900 trading pairs, suffered a critical securit
BITPoint Exchange Hack — $23M Customer Cryptocurrency Stolen, July 2019
Exchange custody
Constrained 2019
On July 12, 2019, BITPoint, operated by Tokyo-listed Remixpoint Inc., discovered unauthorised outflows totalling approximately 3.5 billion yen ($32 million USD)
Bitfinex Fiat Withdrawal Freeze: Crypto Capital Processing Delays October–November 2018
Exchange custody
Constrained 2018
Bitfinex paused fiat deposits in October 2018 and announced implementation of a new deposit system. The exchange had been routing USD withdrawals through Crypto
CHBTC Bitcoin Withdrawal Suspension Under PBOC Regulatory Order (February–mid-2016)
Exchange custody
Constrained 2016
In late January and early February 2016, China's People's Bank (PBOC) convened meetings with major Bitcoin exchanges to mandate upgraded Know Your Customer (KYC
Poloniex Suspends New Hampshire Operations, Forces User Withdrawals by October 6, 2016
Exchange custody
Constrained 2016
In September 2016, Poloniex, a major US-based cryptocurrency exchange known for altcoin trading, announced a service suspension affecting all New Hampshire resi
OKCoin Bitcoin Withdrawal Freeze: PBOC Regulatory Action Extends 4 Months (February–June 2016)
Exchange custody
Constrained 2016
The People's Bank of China initiated regulatory inspections of OKCoin, Huobi, and BTCC in early January 2016, identifying serious compliance gaps: illegal margi
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
Vault of Satoshi Exchange Closure: Institutional Custody Dependency and Forced Withdrawal Deadline
Exchange custody
Constrained 2015
Vault of Satoshi, a Canadian cryptocurrency exchange launched in October 2013, announced permanent closure effective February 5, 2015. The platform had differen
Kraken Exchange DDoS Attack — Users Locked Out During November 2015 Extortion Siege
Exchange custody
Constrained 2015
Kraken, a US-registered cryptocurrency exchange founded in 2011, received an extortion letter in November 2015 demanding Bitcoin payment in exchange for cancell
CAVIRTEX Closure and Withdrawal Delays: February–March 2015
Exchange custody
Constrained 2015
CAVIRTEX, a Canadian Bitcoin exchange, announced its closure on February 17, 2015, following discovery of a database compromise involving older user information
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
Mt. Gox Exchange Collapse: 850,000 BTC Lost, 127,000 Creditors, 10-Year Recovery
Exchange custody
Constrained 2014
Mt. Gox operated as the world's primary Bitcoin exchange from 2006 onward, handling over 70% of global Bitcoin transaction volume at its peak. The platform func
FXBTC Shanghai Exchange Premature Closure Blocks Customer Withdrawals
Exchange custody
Blocked 2014
FXBTC was a Shanghai-based cryptocurrency exchange operating during China's early Bitcoin trading boom. In early May 2014, following escalating regulatory press
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
Mt. Gox SEPA Withdrawal Delayed 28 Days: lukcoin's Unresolved Case (May 2013)
Exchange custody
Indeterminate 2013
On May 7, 2013, BitcoinTalk user lukcoin posted in the Mt. Gox withdrawal delays thread describing a SEPA transfer initiated on April 9 that had not arrived aft
Institutional lockout — Mt. Gox (2013)
Exchange custody
Indeterminate 2013
On April 8, 2013, BitcoinTalk Legendary-ranked user el_rlee submitted a withdrawal request to Mt. Gox. Twelve days later, on April 20, el_rlee posted in a gathe
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
← PreviousNext →
Structural dependencies
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