CustodyStress
Archive › Documentation absent
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00130

Documentation absent — exchange custody (2014)

Blocked
Case description
Multiple Bitcoin-based investment programs that had operated in 2013–14 became dormant in Q3 2014 as Bitcoin's price fell. They had accepted BTC with no written contracts, no withdrawal terms, no documented return schedule, and no on-chain proof of reserve. When operators went silent, investors had no paper trail to pursue legal action.
Custody context
Stress conditionDocumentation absent
Custody systemExchange custody
OutcomeBlocked
DocumentationUnknown
Year observed2014
CountryUnknown
Structural dependencies observed
Undocumented procedure
What this illustrates
Nobody had written down how to get back in. That knowledge existed only in the owner's head. Access was not recoverable.
Outcome interpretation
Access was not possible under the reported conditions.
Source
Publicly Reported
Evidence type
Forum post
Related cases involving documentation absent
193 cases involve documentation absent 512 cases involve exchange custody 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
Terms guide
Survives
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.
Single-person knowledge
Recovery depended on information or capability held by one individual who was unavailable.
Institutional dependence
Recovery depended on a third-party institution or service that was inaccessible or uncooperative.
Documentation gap
Recovery depended on instructions that were missing, incomplete, or unclear.
Authority mismatch
The person with legal authority to act did not have operational access, or vice versa.
Original text
Rate this translation
Your feedback will be used to help improve Google Translate