CustodyStress
Archive › Browse by outcome and custody type › Indeterminate — Exchange custody
Part of the CustodyStress archive of observed Bitcoin custody incidents
IndeterminateExchange custody

Indeterminate — Exchange custody

Cases where an exchange-related access failure has an unknown or unresolved outcome. Many exchange failure cases remain indeterminate because claims processes are ongoing or final distributions have not been documented.

77 observed cases
Indeterminate
77 (100%)
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
Coinbase Bitcoin Inheritance Without Estate Plan or Recovery Instructions
Exchange custody
Indeterminate 2015
A Bitcoin advocate died by suicide in March, leaving approximately $15,000 USD in Bitcoin held on Coinbase. The deceased had not designated a recovery contact,
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
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
Forgotten Password on Blockchain.info: 0.22 BTC Access Lost, Brute-Force Recovery Attempted
Exchange custody
Indeterminate 2014
In October 2014, a BitcoinTalk forum user reported that their friend had become locked out of a blockchain.info wallet containing 0.22 BTC after forgetting the
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
Blockchain.info Two-Factor Authentication Lockout: Correct Credentials Rejected
Exchange custody
Indeterminate 2013
On April 21, 2013, Narydu, operator of bitcoinargentina.org, lost access to a Blockchain.info hosted wallet despite possessing both the correct primary password
Mt. Gox SEPA Withdrawal Vanishes: mably's €EUR Transfer Confirmed But Never Received
Exchange custody
Indeterminate 2013
On April 6, 2013, BitcoinTalk user mably received email confirmation from Mt. Gox that a SEPA EUR withdrawal had been initiated. Twenty days elapsed without the
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
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 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
50btc Pool Mining Loss: 2–3 BTC Trapped in Defunct Pool, Virtual Disk Recovery Failed
Exchange custody
Indeterminate 2010
In 2010, a user identified as Zagal downloaded and ran 50miner, a mining client for the 50btc pool, on his personal computer for approximately one week. During
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
Pheeva Mobile Wallet Collapse: 4 BTC Inaccessible After Passphrase Authentication Failure
Exchange custody
Indeterminate
Between 2014 and 2015, a Bitcoin user deposited approximately 4 BTC into Pheeva, a mobile wallet application developed by Lamar Wilson's Love Will company. The
Unverified WIF Key Found After Brother's Death; Blockchain.com Wallet Remains Inaccessible
Exchange custody
Indeterminate
A man had invested shared family funds in a Bitcoin wallet on blockchain.com approximately 10 years before his death. He left no recovery instructions, seed phr
Cavirtex Exchange Shutdown and Withdrawal Lockdown (March 2015)
Exchange custody
Indeterminate
Cavirtex, a Canadian Bitcoin and Litecoin exchange founded in late 2011, discovered a compromise of an older database version on February 15, 2015. The breach e
← PreviousNext →
Browse by outcome and custody type
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