In one minute
Unocoin's incident brings the limits of a platform-level wallet freeze into focus. Separately, two new CFTC lawsuits put federal and state authority over prediction markets in dispute. Both stories have fresh primary accounts and unresolved consequences.
The lead story
The key combination that can bypass a platform freeze
BitGo's account of the Unocoin incident says the exchange used a two-of-three self-custody wallet. Unocoin held a user key and a backup key, while BitGo held the third. BitGo says its enterprise account freeze blocked requests through its platform and prevented its own key from signing, but could not stop an independently broadcast transaction signed with the two customer-held keys.
Why now: BitGo's November account describes wallet activity after an enterprise freeze. The incident has affected access to the exchange, so the distinction between a service control and control over an on-chain wallet is immediately relevant to users.
An angle worth explaining: A two-of-three threshold creates a recovery path if one key is unavailable. That resilience also means the remaining valid pair can authorize a transaction without the missing signer. A freeze applied by one provider therefore has a defined perimeter: it can stop that provider's signing and platform requests, while the blockchain will still accept a transaction meeting the wallet's rules. An account freeze and a protocol-level restriction are separate controls.
This raises a specific question for customers and operators: which parties hold the keys, what combinations can authorize transfers, and which emergency action can actually stop each route? Backups reduce dependence on a single provider but must be protected as active signing authority, not treated as inert archives. The structure can work as designed while the operational response falls short of a user's expectation of what a freeze means.
What remains uncertain: BitGo's description is the account of a party involved in the incident. The full cause, total loss and final recovery outcome require evidence beyond the company's explanation of the signing arrangement.
More stories worth covering
CFTC challenges state restrictions in two new cases
On November 13, the CFTC announced separate lawsuits involving Arkansas and Louisiana. The federal regulator says it is defending the availability of event contracts offered by federally regulated entities; Arkansas has brought a state proceeding against Kalshi, according to the agency.
Why now: The two filings add fresh legal steps to a continuing dispute over who can regulate prediction-market contracts. They concern access to a market that creators and their audiences encounter through platforms and wallet interfaces.
An angle worth explaining: Federal designation and state enforcement are distinct layers. A platform may point to federal oversight, while a state argues that particular activity falls within its own laws. The lawsuit asks courts to resolve the legal conflict for the parties and remedies at issue. The filing itself does not settle whether a contract will remain available to a particular user in a particular state.
What remains uncertain: The CFTC's press releases describe its position, not a final judgment. The states' responses, court orders and the scope of any relief matter more than a headline announcing a lawsuit.
Sources (3)
- BitGo's account of the Unocoin incidentwww.bitgo.com, Publication date not specified
- Arkansaswww.cftc.gov, Publication date not specified
- Louisianawww.cftc.gov, Publication date not specified