Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00033
Documentation absent — exchange custody (2013)
BlockedCase description
When Inputs.io shut down in October 2013 after the double hack, TradeFortress posted a statement on Bitcointalk acknowledging the losses but providing no breakdown of which wallets were affected, no list of impacted wallet addresses, and no documentation of pre-hack balances. Customers could not independently verify their individual loss without this data.
Custody context
| Stress condition | Documentation absent |
| Custody system | Exchange custody |
| Outcome | Blocked |
| Documentation | Unknown |
| Year observed | 2013 |
| Country | Australia |
Structural dependencies observed
What this illustrates
There was no documentation of how access worked. Without it, there was no path back in. Access was not recoverable.
Outcome interpretation
Access was not possible under the reported conditions.
Source
Publicly Reported
Evidence type
News article
Related cases involving documentation absent
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.
Translate