CustodyStress
ArchiveUndocumented Recovery Procedure › Vendor Lockout
Part of the CustodyStress archive of observed Bitcoin custody incidents

Undocumented Recovery Procedure — Vendor Lockout

Cases where no written procedure existed for how recovery would be executed. The holder understood the arrangement; no record existed to guide anyone else. This page shows archive cases where both conditions were present.

26% of all Vendor Lockout cases in the archive involve this structural dependency. Among them, 64% of determinate cases resulted in a blocked outcome. The most common recovery path is exchange support.

14
Blocked
5
Constrained
3
Survived
29
Indeterminate

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

51 observed cases
Blocked
14 (27%)
Constrained
5 (10%)
Survived
3 (6%)
Indeterminate
29 (57%)
Blockchain.info Legacy Wallet Lockout: 17-Word Phrase Incompatible With Recovery Tool
Exchange custody
Indeterminate 2017
Between November and December 2017, multiple Blockchain.info users discovered they could not access legacy wallets created years earlier, despite possessing com
Blockchain.info Wallet Access Blocked by Lost Wallet ID Despite Valid Recovery Phrase
Exchange custody
Indeterminate 2017
In December 2017, a Bitcoin holder discovered that custody of funds deposited in a Blockchain.info wallet created in early 2013 had become inaccessible despite
Blockchain.info Legacy Wallet Access Failure: 17-Word Recovery Phrase Incompatibility
Exchange custody
Blocked 2017
Beginning in late November 2017, multiple users including Ople, nwankwotech, and Boldos reported simultaneous access failures to Blockchain.info wallets created
Blockchain.info 2FA Email Delivery Failure — December 2017 Access Lock
Exchange custody
Constrained 2017
In early December 2017, the user crando discovered they could not access their Blockchain.info hosted wallet after the platform failed to deliver two-factor aut
Custodial Wallet Provider Bankruptcy: 2012 Bitcoin Purchase Permanently Inaccessible
Exchange custody
Blocked 2017
In November 2017, a Bitcoin holder disclosed that they had purchased Bitcoin in 2012 but subsequently lost access to their holdings after the company maintainin
Mycelium Mobile Wallet Balance Access Failure — December 2017
Software wallet
Indeterminate 2017
In mid-December 2017, a Bitcoin user (Myrr) discovered a critical custody access failure in the Mycelium mobile wallet on their iPhone. The user had purchased B
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
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
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
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
Armory Wallet Synchronization Failure: Access Restored After Software Upgrade
Software wallet
Survived 2013
In October 2013, a BitcoinTalk user holding approximately 0.1008 BTC in an encrypted Armory wallet encountered a critical access failure. The user possessed bot
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 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
GreenAddress User Locked Out by 2FA Requirement Despite Mnemonic Backup
Collaborative custody
Constrained
A GreenAddress user transferred Bitcoin from Bitfinex to a GreenAddress multisig wallet, securing an encrypted backup of their recovery mnemonics using their Br
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
Mycelium Mobile Wallet Glitch: Bitcoin Inaccessible Despite Blockchain Confirmation
Software wallet
Blocked
In February 2020, a Bitcoin user purchased coins on the Mycelium mobile wallet application. Shortly after the purchase, the user attempted to create a backup bu
Blockchain.info Account Inaccessible: Valid Credentials Defeated by Email Verification Gate
Exchange custody
Blocked
An early adopter maintained a Blockchain.info wallet account from the platform's initial era, retaining both the wallet ID and a valid password. The account rem
BitGo Wallet Permanently Inaccessible: Lost 2FA Device and Missing Documentation
Exchange custody
Blocked
A long-term Bitcoin holder maintained a BitGo-hosted wallet from 2015 without establishing comprehensive backup procedures or written documentation. The account
BTC.com Wallet Closure: Recovery Documents Present but Platform Inaccessible
Exchange custody
Indeterminate
BTC.com, a web-based wallet service, announced cessation of operations effective April 15. The user discovered the service was non-functional upon attempting lo
Samourai Wallet Balance Lost After Android Downgrade — Recovered via Older APK
Software wallet
Survived
The user maintained a deliberate hybrid custody model: cold storage via Tails-generated paper wallets and a Digital Bitbox hardware wallet for larger holdings,
BitGo Account Lockout: Forgotten Password, Inaccessible Recovery Email, Circular Dependency
Exchange custody
Blocked
A BitGo user faced complete account lockout after simultaneously losing access to two critical elements: the login password and the email address registered to
LUNO Exchange Account Access Failure: Email Identifier Lockout
Exchange custody
Constrained
In 2013, a Bitcoin holder received cryptocurrency from BitX (later rebranded as LUNO) and deposited the funds directly on the exchange platform. For several yea
← PreviousNext →
Related archive views
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