Part of the CustodyStress archive of observed Bitcoin custody incidents

Browse archive Archive statistics Scenarios Dependencies About

CS-00771

BlockTrail Wallet Recovery Blocked: Paper Backup Orphaned After Service Discontinuation

Indeterminate

Custodial platform became inaccessible — whether funds were recovered is not documented.

Case description

A Bitcoin holder discovered a printed paper backup from BlockTrail, a non-custodial wallet service that used 2-of-3 multisig and hierarchical deterministic key derivation. The backup contained a BlockTrail wallet identifier (v3), encrypted primary seed, backup seed, encrypted recovery secret, and two QR codes. Printed instructions on the backup directed the user to blocktrail.com/recovery to restore their funds.

BlockTrail was founded in Amsterdam in 2014 and gained traction for offering users full control over their private keys through multisig architecture. The company was acquired by Bitmain in July 2016 and gradually integrated under BTC.com branding. Active development ceased years before the official service discontinuation announced in April 2022.

When the user attempted to access the recovery URL specified on their paper backup, the page no longer existed. The service infrastructure had been retired as part of the platform wind-down. Although the backup itself contained all necessary cryptographic material—encrypted seeds, wallet identifier, and recovery secret—the specific recovery tool needed to use that material was no longer operational at the documented URL.

Investigation within the recovery community suggested that an official recovery tool might theoretically be accessible at recovery.blocktrail.com (a different domain from the primary blocktrail.com), but its current operational status and accessibility remained unclear and unverified. The user faced a technical and informational barrier: the backup was genuine and complete, but the institutional infrastructure required to interpret and use it had vanished. Community responses emphasized caution against private solicitation offers, noting that any legitimate assistance would be offered publicly on technical forums. The case remained unresolved within the documented thread.

Custody context

Stress condition	Vendor lockout
Custody system	Multisig (self-managed)
Outcome	Indeterminate
Documentation	Partial

Structural dependencies observed

What this illustrates

There was no documentation of how access worked. Without it, there was no path back in. A self-managed multisig setup distributes signing authority across multiple keys. This protects against single-key compromise but introduces coordination requirements that can become barriers when key holders are unavailable. Custodial arrangements shift the locus of control from the holder to the institution. When the institution becomes unavailable — through insolvency, regulatory action, or policy change — so does access. An indeterminate outcome reflects the limits of available information. Whether anyone eventually gained access is not documented in the sources reviewed.

Why this matters

Why custodial Bitcoin fails differently than self-custody

Vendor lockout cases follow a pattern that is structurally different from all other stress conditions in the archive. In self-custody failures, the problem is credentials — missing keys, forgotten passphrases, undiscovered backups. In vendor lockout, the credentials are often intact. The problem is that the institution that was supposed to honor them is no longer accessible.

Exchange custody transfers the custody problem from the holder to the institution. The holder no longer needs to manage seed phrases, maintain hardware, or understand cryptographic concepts. They need only to maintain their account. This simplicity has a cost: the holder no longer controls the private keys. Access depends entirely on the continued operational, financial, and regulatory health of the exchange.

Cases in this archive show that exchange failures cluster around specific event types: bankruptcy and insolvency, regulatory seizure, geographic sanctions, and account-level access failures (lost 2FA, forgotten email credentials). Each event type has a different recovery path and a different timeline. Bankruptcy proceedings typically take 6-24 months and produce partial recovery. Regulatory seizure timelines depend on legal process. Account access failures may be resolvable through platform support or may not.

The distinguishing feature of vendor lockout cases is that recovery — when it occurs — happens through processes the holder did not design and cannot control. They become claimants in a process rather than holders of an asset.

How this category of failure is typically preventable

The primary protection against vendor lockout is not using a vendor for custody beyond what is needed operationally. Holdings intended to be stored long-term are most exposed to institutional risk. Exchange custody is well-suited for active trading and conversion; it is poorly suited for long-term storage of significant value. Moving Bitcoin off exchange into self-custody eliminates platform dependency at the cost of taking on personal custody responsibility.

Frequently asked questions

What happens to Bitcoin if the exchange goes bankrupt?

Bankruptcy freezes customer assets during proceedings. Account holders typically cannot withdraw during this period. Depending on the jurisdiction, exchange custody, and bankruptcy structure, customers may recover some or all of their Bitcoin through the bankruptcy process — but this takes months to years, requires filing claims, and frequently results in partial recovery. Cases where the exchange operated with insufficient reserves produce the worst outcomes.

Is Bitcoin on an exchange safe?

Exchange-held Bitcoin carries platform dependency risk that self-custody does not. The exchange controls the private keys, not the holder. Platform insolvency, regulatory action, account freezes, or technical failures can all restrict access. The phrase "not your keys, not your coins" reflects this: without controlling the private keys, the holder depends entirely on the continued operation of the exchange.

Can an exchange freeze or block access to Bitcoin?

Yes. Exchanges can restrict access due to regulatory compliance requirements, suspicious activity flags, identity verification failures, sanctions compliance, court orders, or their own technical or financial problems. Self-custody Bitcoin cannot be frozen by a third party — it can only be moved by whoever holds the private keys. Exchange custody eliminates this property.

Source

Publicly Reported

Evidence link

https://www.reddit.com/r/Bitcoin/comments/1o1j5qw/help_with_recovering_my_bitcoin

Most structurally similar case

BTC.com Multi-Sig Wallet Recovery Failure: Non-Standard Derivation Path Lockout

Vendor lockout · Multisig (self-managed) · 2023 Indeterminate

Related cases

Structural patterns in this case

Exchange bankruptcy

193 cases involve vendor lockout 4 cases involve multisig (self-managed) View archive statistics →

This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case

← All cases

Framework references

Where Bitcoin Custody Intersects Legal and Fiduciary Authority

Where custody creates gaps in estate planning, fiduciary duty, and professional responsibility.

Professional Scope Boundary Matrix

What each professional or product covers, what they do not, and where gaps form between them.

The Independent Assessment Layer in Bitcoin Custody

How independent diagnostic layers emerge when multiple parties depend on shared infrastructure.

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:

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.
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.
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.