CustodyStress
Archive › Browse by documentation status and outcome › Partial Documentation — Survived
Part of the CustodyStress archive of observed Bitcoin custody incidents
PartialSurvives

Partial Documentation — Survived

Cases where partial documentation existed and recovery still succeeded. These cases document the minimum viable documentation threshold — what partial records enabled recovery and what did not.

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

Archive analysis — 34 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
62% of cases involved software wallet, followed by exchange custody at 12%.
Primary stress condition
50% of cases involve passphrase unavailable. Documentation absent accounts for a further 12%.
Recovery path
Password Bruteforce is the most documented recovery path (13 cases, 38% of subset). Of those with a determinate outcome, 100% resulted in recovered or constrained access.
Documentation
100% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Structural dependency
68% of cases carry a device-dependent access dependency tag — the most common structural factor in this subset.
0
Blocked
0
Constrained
34
Survived
0
Indeterminate

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

34 observed cases
Survived
34 (100%)
Taehwa Kim: Kidnapped Bitcoin Trader Resists Coercion in Philippines
Hardware wallet (single key)
Survived 2025
Taehwa Kim, a Korean Bitcoin trader, was kidnapped in Makati, Philippines in January 2025. He was held hostage for three days by assailants who sought to extrac
Italian Crypto Entrepreneur Survives Torture Ordeal in Manhattan, Keeps Bitcoin
Unknown custody system
Survived 2025
In May 2025, a 28-year-old Italian cryptocurrency entrepreneur based in New York City was abducted and held captive in a luxury Manhattan apartment for several
Goiania Wrench Attack: Physical Coercion Attempt on Bitcoin Holder Thwarted by Police
Unknown custody system
Survived 2025
In June 2025, a cryptocurrency-holding businessman in Goiania, Brazil was lured to what appeared to be a legitimate business meeting. The location was instead a
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
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
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
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
Forgotten Bata Wallet Passphrase Recovered by Professional Service
Software wallet
Survived 2017
On August 1, 2017, a BitcoinTalk user operating under the handle InvestMeDaddy posted a recovery request after losing access to a Bata desktop cryptocurrency wa
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
Paper Wallet Private Key Recovery: Reconstructing Corrupted Font-Rendered WIF
Software wallet
Survived 2014
In 2014, a Bitcoin holder generated a paper wallet using a widely available online paper wallet generator tool. The printed document contained both a public add
Forgotten Passphrase Locks Desktop Wallet for 8 Years; btcrecover Enables Recovery
Software wallet
Survived 2013
In 2013, this individual created a Bitcoin wallet using desktop software, securing it with a passphrase. The holder subsequently lost memory of that passphrase
Norwegian Student Successfully Recovered Forgotten Bitcoin Wallet Password From 2009
Software wallet
Survived 2009
In 2009, a Norwegian student purchased approximately $27 worth of Bitcoin as part of an academic exploration of the emerging cryptocurrency. The purchase and wa
18 BTC Bitcoin-Qt Wallet.dat: Database Corruption and Filesystem Recovery
Software wallet
Survived
A Bitcoin holder possessed an early Bitcoin-Qt wallet file containing 18 BTC that had been abandoned for years after the wallet appeared corrupted. When Bitcoin
Forgotten Bitcoin Wallet Passphrases: Forum Cases of Successful Third-Party Recovery (2014–2021)
Software wallet
Survived
Between 2014 and 2021, seven Bitcoin holders posted testimonials on a forum documenting their recovery of wallets encrypted with forgotten passphrases. Cases ra
Mark Frauenfelder's 7 Bitcoin: Household Cleaner Discards Written Seed Phrase
Hardware wallet (single key)
Survived
Mark Frauenfelder, a US journalist, purchased approximately 7 Bitcoin in early 2016 at roughly $3,000 total investment. As the asset price appreciated significa
Recovering Encrypted MultiBit Private Key When Decryption Method Is Forgotten
Software wallet
Survived
In April 2021, a Bitcoin holder sought recovery of a private key they had exported from MultiBit Classic years earlier. The key had been written to a text file
Recovering a Deceased Father's 14 BTC from Blockchain.com via Email Access
Exchange custody
Survived
A Reddit user reported successfully recovering 14 BTC held in a Blockchain.com wallet belonging to their deceased father approximately six months after the deat
Bitcoin.com Wallet: 1.55 BTC Recovery via Undocumented Keychain Export After Seed Loss
Software wallet
Survived
In July 2020, a Bitcoin.com mobile wallet user performed an app uninstall and reinstall without first recording the wallet's seed phrase. The app was marketed a
Passphrase Recovery Success and OPSEC Failure: 2014 WalletRecoveryServices Case
Software wallet
Survived
A Bitcoin holder in 2014 created private keys but lost the passphrase required to access them. The funds remained locked for an unknown duration until the owner
BIP38 Paper Wallet: Seven-Year Inaccessibility Resolved via Single-Character Error
Software wallet
Survived
In 2017, an individual encrypted a paper wallet using BIP38 encryption, protecting it with a passphrase derived from their favorite band—a mnemonic they believe
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
Hardware Wallet Backup Complete — Bitcoin Never Left the Exchange
Exchange custody
Survived
An estate executor discovered a Trezor Safe 3 hardware wallet in the deceased's bedside table alongside a 12-word seed phrase and PIN. Bank records showed a $1,
4 BTC Lost Behind Forgotten Passphrase After Ledger PIN Lockout
Hardware wallet with passphrase
Survived
The user maintained a Ledger Nano S hardware wallet configured with two separate accounts: a primary account secured by a 24-word BIP39 seed phrase stored in co
← PreviousNext →
Browse by documentation status 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