CustodyStress
ArchiveVendor lockout › Exchange custody
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00574

Genesis Global Capital Freezes $900M in Gemini Earn Bitcoin — Retail Users Locked Out

Constrained

Custodial platform became inaccessible — recovery ran through a lengthy institutional process.

Case description

Throughout 2022, Genesis Global Capital—the cryptocurrency lending subsidiary of Digital Currency Group—accumulated exposure to failing counterparties and deteriorating market conditions. After Three Arrows Capital defaulted on a $1.2 billion loan in summer 2022 and FTX's bankruptcy filing on November 11, 2022, Genesis held $175 million in locked FTX funds it could not liquidate. The bankruptcy triggered a cascade of customer withdrawal requests Genesis could not fulfill.

On November 16, 2022, Genesis suspended all redemptions and new loan originations, immediately freezing approximately $900 million belonging to 340,000 retail users enrolled in Gemini Earn—a yield-bearing custody product marketed by Gemini (the exchange operated by Cameron Winklevoss and Tyler Winklevoss) where customers lent their Bitcoin and other assets to Genesis in exchange for monthly interest payments. Genesis users had believed their assets remained accessible through a regulated exchange; instead, they discovered their funds were locked inside an opaque multi-tier institutional lending chain over which they had no control. Gemini CEO Cameron Winklevoss publicly accused DCG of fraud. Genesis filed Chapter 11 bankruptcy in the Southern District of New York on January 19, 2023.

The SEC charged Genesis and Gemini with selling unregistered securities; Genesis settled for $21 million. New York's attorney general sued DCG and Gemini for fraud; the settlement reached in May 2024 totaled $2 billion. Genesis's restructuring completed in August 2024, distributing approximately $4 billion to creditors. Bitcoin creditors recovered 51.

28% of their holdings in kind, Ethereum creditors 65.87%, and Solana creditors 29.58%. The incident exposed the structural fragility of yield products that obscure the actual custody chain and counterparty risk from retail users.

Custody context
Stress conditionVendor lockout
Custody systemExchange custody
OutcomeConstrained
DocumentationPresent and interpretable
Year observed2022
CountryUnited States
Structural dependencies observed
Single Person KnowledgeShared Vendor RootInstitutional cooperation requiredLegal Authority Required
What this illustrates
Only one person knew how the setup worked — and that person wasn't available. Exchange custody eliminates key management complexity but replaces it with platform dependency. The holder does not control private keys — access runs entirely through the platform. 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. The funds were held by a third party. When that party became unavailable, so did the Bitcoin. A constrained outcome means access was eventually possible, but required significant effort, outside assistance, or time — none of which were built into the original setup.
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.

Read more: Bitcoin Exchange Custody Risks →
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
Most structurally similar case
FTX Exchange Collapse Freezes 1+ Million Customer Accounts — November 2022
Vendor lockout · Exchange custody · 2022 Constrained
Related cases
Structural patterns in this case
Exchange bankruptcy
193 cases involve vendor lockout 265 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
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