CustodyStress
Archive › Browse by dependency and custody › Undocumented Recovery Procedure — Exchange custody
Part of the CustodyStress archive of observed Bitcoin custody incidents
Undocumented Recovery ProcedureExchange custody

Undocumented Recovery Procedure — Exchange custody

Cases where no documentation existed for how to access an exchange account. Exchange account recovery typically requires specific identity documents, email access, and procedural knowledge that heirs frequently lack.

32% of all Exchange custody cases in the archive involve this structural dependency. The blocked rate among them is 74% — 5 points above the archive-wide blocked rate of 69%. The most common recovery path is exchange support.

29
Blocked
6
Constrained
4
Survived
46
Indeterminate

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

85 observed cases
Blocked
29 (34%)
Constrained
6 (7%)
Survived
4 (5%)
Indeterminate
46 (54%)
Blockchain.info Legacy Wallet: Mnemonic Present, Backup File Present—Funds Inaccessible
Exchange custody
Blocked 2015
In 2015, the user created a Blockchain.info wallet and purchased Bitcoin, then implemented two backup strategies: a 17-word legacy mnemonic phrase and an encryp
Forgotten Blockchain.info Password: Client-Side Encryption Locks €100 Bitcoin Permanently
Exchange custody
Blocked 2015
On September 17, 2015, a Blockchain.info user with the forum username Seporstia posted requesting help recovering access to a hosted wallet after forgetting the
Blockchain.info Account Lockout: Forgotten Password, Missing Seed Phrase, $3,800 USD Inaccessible
Exchange custody
Indeterminate 2015
TheLoser created a hosted wallet on Blockchain.info via the Apple mobile application in late September 2015. The wallet creation process did not present or prov
Blockchain.com 2015 Private Key Encoding Bug: 0.48 BTC Permanently Inaccessible
Exchange custody
Indeterminate 2015
In August 2022, a user identified as montythegoat discovered an old Blockchain.com wallet on their Google Drive while cleaning archived files. The wallet had be
Blockchain.info iOS Wallet: $3,600 Lost to Missing Mnemonic and Unresettable Password
Exchange custody
Blocked 2015
In September 2015, TheLoser created a Bitcoin wallet on Blockchain.info using an iOS mobile device. Unlike documented Blockchain.info workflows, the wallet crea
0.3 BTC Lost After Uninstalling Blockchain.info Desktop Wallet Without Backup
Exchange custody
Blocked 2015
In June 2015, a user identified as Williams2017 received approximately 0.3 BTC (then valued at roughly $70 USD) from an entity called 'www.instantgold.ng' to th
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
Lost Blockchain.info iOS Wallet Password (2014) — Recovery Attempt via BTCRecover
Exchange custody
Indeterminate 2014
In December 2021, a BitcoinTalk user identified as Quix77 disclosed loss of access to a Blockchain.info wallet created in August 2014 via the iOS Blockchain app
Forgotten Blockchain.info Password: 0.22 BTC Trapped Behind AES Encryption
Exchange custody
Indeterminate 2014
On October 8, 2014, a BitcoinTalk forum user findftp described his friend's predicament: access lost to a Blockchain.info wallet containing 0.22 BTC due to a fo
Password Safe Crash Leaves Blockchain.info Wallet Inaccessible
Exchange custody
Indeterminate 2014
In January 2014, a BitcoinTalk user identified as StinkyS4L discovered that their Password Safe application had crashed, rendering all stored passwords inaccess
Lost Access to 2014 blockchain.info Wallets: Non-Standard Recovery Mnemonics, No Support Response
Exchange custody
Indeterminate 2014
In July 2020, forum user gbola reported locating five recovery mnemonics created circa 2014 when blockchain.info was in its early operations. The user's entire
Blockchain.info Two-Factor Authentication Reset Declined — November 2014
Exchange custody
Constrained 2014
On November 15, 2014, a Blockchain.info user enabled two-factor authentication using Google Authenticator on an Android phone but failed to back up the QR code
Forgotten Password on Blockchain.info Web Wallet: 0.22 BTC Inaccessible
Exchange custody
Indeterminate 2014
In October 2014, a Bitcoin Forum user (findftp) sought technical assistance for a friend who had lost access to a Blockchain.info wallet containing 0.22 BTC (ap
Forgotten Blockchain.info Password: 0.22 BTC Recovery Attempt via Brute-Force
Exchange custody
Indeterminate 2014
In October 2014, a BitcoinTalk forum user (findftp) posted on behalf of a friend who had lost the password to a Blockchain.info web wallet containing 0.22 BTC (
Blockchain.com 2014 Hosted Wallet: Password and Seed Phrase Loss
Exchange custody
Indeterminate 2014
A Blockchain.com customer acquired approximately 0.5 BTC in 2014 using the platform's hosted wallet service. Over the years, the original password and recovery
0.5 BTC Lost in Blockchain.info Encrypted Wallet (2014)
Exchange custody
Indeterminate 2014
In January 2014, an early Bitcoin adopter purchased BTC on LocalBitcoins and transferred 0.5 BTC to a public address in August of that year. The user recorded o
Blockchain.info Hosted Wallet Lockout: Decryption Error and Recovery via Desktop Import
Exchange custody
Indeterminate 2013
In March 2013, a Blockchain.info user ('key2') encountered a critical access failure on the platform's hosted wallet service shortly after their first Bitcoin p
Blockchain.info Android Wallet PIN-Only Setup Access Failure (2013)
Exchange custody
Indeterminate 2013
In June 2013, a user known as NeedChangeNow created a mobile Bitcoin wallet using Blockchain.info's Android application on a Samsung Galaxy S4 running Android 4
2013 Blockchain.info AES-Encrypted Wallet: Password Lost, Recovery Tooling Exhausted
Exchange custody
Indeterminate 2013
In March 2013, during a two-month personal mining experiment, a user registered a wallet on blockchain.info and received an AES-encrypted backup file via email
Blockchain.info Web Wallet (2013): Silent Login Failure, Unresolved After 3 Months
Exchange custody
Blocked 2013
In late 2013, a user created a Bitcoin wallet on blockchain.info, then one of the most popular web-based custodial platforms. The wallet remained accessible dur
Blockchain.info Web Wallet: Imported Private Key Vanished After Sync Popup
Exchange custody
Blocked 2013
In February 2013, a BitcoinTalk user (BurtW) generated a vanity address using vanitygen and imported the private key into his Blockchain.info web wallet account
Blockchain.info Access Blocked After Platform Software Update
Exchange custody
Constrained 2013
A Blockchain.info user experienced sudden access denial to their hosted wallet following a platform software update. The incident occurred in an era when web-ba
Blockchain.info 2013–2014 Wallet Access Failure: Encrypted Files, Lost Password, Functional Recovery Phrase
Exchange custody
Indeterminate 2013
User 'marvin42' created Bitcoin wallets via blockchain.info in 2013 or 2014 and retained two AES-encrypted backup files dated 28 February 2014 and 22 April 2013
Coinkite Platform Shutdown: Encrypted Private Key Available, Recovery Status Indeterminate
Exchange custody
Indeterminate
In 2014, a Bitcoin newcomer purchased BTC via Coinkite, an online hosted wallet service. The user then disengaged entirely from cryptocurrency for several years
Lost Access to Blockchain.info Wallet Without Identifier or Mnemonic
Exchange custody
Indeterminate
A disabled user in the United States was introduced to Bitcoin by their son, who created two blockchain.info wallets and taught them to use faucets as an activi
← PreviousNext →
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