ThrillHou v. Cryptsy: Account Lockout, KYC Data Misuse, and Alleged Identity Compromise
BlockedCustodial platform became inaccessible — the holder had no independent key control.
ThrillHou, a Cryptsy user, experienced repeated account lockouts beginning in 2015. When support staff operating under aliases BigJohn and John McPherson repeatedly requested password resets, ThrillHou grew suspicious. The pattern suggested not a technical glitch but a deliberate cycle: Cryptsy was allegedly forcing a new password, then locking the account against it, creating an endless loop of inaccessibility.
The situation escalated during KYC verification. Cryptsy disputed the accuracy of ThrillHou's Social Security Number—an interaction ThrillHou interpreted as evidence the exchange had attempted unauthorized use of the SSN for fraudulent purposes. Within weeks of providing Cryptsy with their home address, ThrillHou reported receiving unusual postal mail, suggesting personal data had been sold or improperly shared.
After BigJohn allegedly requested the matter be handled privately—and lockouts persisted—ThrillHou engaged legal counsel. Attorneys recommended filing a complaint with the FBI's Internet Crime Complaint Center (IC3). ThrillHou immediately froze personal credit cards and bank accounts as a precaution against identity theft.
Once litigation commenced and credit freezes were in place, Cryptsy support ceased contact entirely. The exchange later issued a dismissive public statement claiming the account issue was merely a routine password reset. ThrillHou's case became the most prominent individual escalation among hundreds of Cryptsy users experiencing account freezes during 2015. The complaint pattern—account manipulation combined with KYC data misuse—formed a core allegation in the subsequent class action filing against the platform.
| Stress condition | Vendor lockout |
| Custody system | Exchange custody |
| Outcome | Blocked |
| Documentation | Present and interpretable |
| Year observed | 2015 |
| Country | United States |
Why custodial Bitcoin fails differently than self-custody
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.
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.