CustodyStress
Archive › Browse by dependency and outcome › Undocumented Recovery Procedure — Survived
Part of the CustodyStress archive of observed Bitcoin custody incidents
Undocumented Recovery ProcedureSurvives

Undocumented Recovery Procedure — Survived

Cases where undocumented recovery procedure dependency produced a survived outcome.

52 cases in this intersection. 0% of determinate cases resulted in a blocked outcome and 100% in access survived. The most common recovery path is technical recovery.

Archive analysis — 52 cases
Outcomes
0% of determinate cases resulted in blocked access — 69 percentage points below the archive-wide average of 69%. 100% resulted in recovered access — above the archive average.
Custody type
77% of cases involved software wallet, followed by hardware wallet (single key) at 8%.
Primary stress condition
46% of cases involve passphrase unavailable. Device loss accounts for a further 21%.
Recovery path
Technical Recovery is the most documented recovery path (19 cases, 37% of subset). Of those with a determinate outcome, 100% resulted in recovered or constrained access.
Documentation
52% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Time distribution
Cases span 2011–2025. Only 10% occurred in 2022 or later — concentrated in earlier periods.
0
Blocked
0
Constrained
52
Survived
0
Indeterminate

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

52 observed cases
Survived
52 (100%)
Partial Seed Backup + Missing Passphrase Flag: BTCRecover Recovery Success
Software wallet
Survived 2025
gab0miner created an Electrum wallet offline using a Linux Live CD on an unspecified date, recording only 11 of the required 12 BIP39 seed words into KeePass al
Ledger Hardware Wallet: Multiple Account Discovery After Failed Seed Verification
Hardware wallet (single key)
Survived 2024
On March 21, 2024, ContourCool attempted a long-deferred security verification of their Ledger hardware wallet by importing their seed phrase into SeedSigner an
Samourai Wallet Seizure: Recovering Bitcoin After Platform Shutdown
Software wallet
Survived 2024
On April 28, 2024, a BitcoinTalk user reported that Bitcoin deposited to their Samourai Wallet became inaccessible following the FBI's shutdown of the platform.
Trezor Passphrase Forgotten After Factory Reset — Successful Recovery via Community Support
Hardware wallet with passphrase
Survived 2024
BTCRSMD, a moderately experienced Bitcoin user, executed a deliberate custody strategy in July 2024. The user purchased Bitcoin via Swan and routed the coins th
Splashboard Trezor Passphrase Recovery: Third-Party Assisted Access Restoration
Hardware wallet with passphrase
Survived 2022
Splashboard, a Bitcoin holder with minimal public forum presence, purchased a Trezor hardware wallet in late 2021 and performed initial setup. During the setup
Forgotten 115-Character Wallet Password Recovered via GPU Typo-Bruteforce
Software wallet
Survived 2019
In August 2017, a Bitcoin enthusiast created a Bitcoin Core wallet secured by a 115-character sentence-based password and wrote it down. In June 2019, when they
Electrum Seed Version 18 Password Recovery: btcrecover Incompatibility Resolved
Software wallet
Survived 2019
In December 2019, a BitcoinTalk user (red14159) discovered a wallet.dat file from an Electrum wallet they had lost access to approximately three years earlier.
Computer Crash with wallet.dat Backup: Bitcoin Core Recovery Without Private Key Export
Software wallet
Survived 2018
In February 2018, a Bitcoin Core user experienced a total computer crash requiring complete system reinstallation. The user had previously used an Armory wallet
Paper Wallet QR Code Case Mismatch: Single Character Locked Access for 2.5 Years
Software wallet
Survived 2018
Al Reno generated an offline paper wallet using bitaddress.org in August 2018, manually printing both public and private keys with QR codes to physical paper. H
Bither Desktop Wallet Application Crash: 3-Year Recovery via Password Rediscovery
Software wallet
Survived 2018
Sygun created a Bither wallet in March 2018 holding approximately 0.019 BTC. At an unspecified point, the Bither application ceased launching entirely—double-cl
MultiBit Classic Password Lock: Recovery Through Backup Key File Import
Software wallet
Survived 2018
A BitcoinTalk user (cluuze130) deposited Bitcoin into MultiBit Classic approximately one year before attempting withdrawal in February 2018. At the time of depo
Blockchain.info Wallet Access Failure: Platform Login System Change (2017)
Exchange custody
Survived 2017
In March 2014, a user created a Blockchain.info-hosted wallet and received a 12-word recovery passphrase as the sole access credential. The user documented the
Non-Standard Recovery Phrase Recovery: Blockchain.info 2013 Wallet with Double Encryption
Exchange custody
Survived 2017
In June 2017, a user attempted to recover Bitcoin stored in a blockchain.info wallet opened in December 2013, approximately four years prior. Access to the acco
Wallet.dat Corruption After Accidental Drive Format — Recovery via Data Recovery and Pywallet
Software wallet
Survived 2017
In July 2017, AleksTo, a newcomer to Bitcoin, accidentally formatted their hard drive, destroying the only local copy of their wallet.dat file. The user immedia
Forgot Trezor PIN and Seed Words: $30,000 Bitcoin Recovery
Hardware wallet (single key)
Survived 2017
In 2017, during Bitcoin's price surge, a user documented their experience losing access to a Trezor hardware wallet containing approximately $30,000 in Bitcoin.
Trezor PIN and Seed Words Forgotten: $30,000 Bitcoin Recovery
Hardware wallet (single key)
Survived 2017
In October 2017, a Trezor hardware wallet user discovered they had forgotten both their PIN and recovery seed words, creating a dual-layer access barrier to app
Hidden Line Feed Character Blocks Bitcoin Core Wallet Access
Software wallet
Survived 2017
In February 2017, scutzi128 documented a Bitcoin Core wallet access failure on the Bitcoin Technical Support forum. The user had encrypted their wallet with a 2
Corrupted 2013 wallet.dat Recovery via Community-Guided Disk Scanning
Software wallet
Survived 2017
In December 2017, a macOS Bitcoin Core user attempted to restore access to two wallet.dat files created in late 2013. The user had downloaded a contemporary ver
Corrupted Encrypted wallet.dat Recovered via Partition-Level Recovery
Software wallet
Survived 2016
In March 2016, a Bitcoin Core user discovered their only backup of an encrypted wallet.dat file had become corrupted, likely due to improper shutdown of Bitcoin
BIP39 Passphrase Confusion: How a Mobile PIN Hid Bitcoin for Five Years
Software wallet
Survived 2016
In mid-2016, the user's Android device failed. They recovered their MyCelium wallet using their seed phrase but found all pre-2016 Bitcoin gone. The wallet show
Bitcoin Core Wallet Corruption: Selective Key Decryption Failure and Community Recovery
Software wallet
Survived 2015
Henke created an encrypted wallet backup on December 20, 2015, containing approximately 4 BTC. After refreshing his Windows 7 system and reinstalling Bitcoin Co
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
Recovering Deleted Bitcoin Core wallet.dat via pywallet: Device Loss and Forensic Key Extraction
Software wallet
Survived 2015
Edgar's Bitcoin Core wallet became inaccessible in 2015 when the wallet.dat file was removed from the active system while the Bitcoin Core client remained open.
Hard Drive Format Recovery: 2 BTC Restored via Sector Scanning and wallet.dat Reconstruction
Software wallet
Survived 2015
In approximately 2015, marilyn4325 formatted a hard drive and installed Windows 10, intending to preserve wallet data via backup first. However, the backup beca
Recovery of Dormant Blockchain.info Wallet via Legacy 20-Word Mnemonic (2017)
Exchange custody
Survived 2014
Roland808, a BitcoinTalk user, discovered a text file on their computer in March 2017 dated from 2014 containing a label 'bitcoin nmemonic' followed by 20 rando
← 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