Monthly volume crossed $50 billion. Yet the code that settles those predictions remains a black box. On August 12, 2026, Hyperliquid Policy Center and Multicoin Capital submitted a joint comment letter to the CFTC regarding the proposed amendments to Regulation 40.11. The letter is not a plea for leniency. It is a surgical request to make the settlement test transparent and the review reasoning public. For anyone who has audited prediction market smart contracts, these two points are the difference between a compliant protocol and a legal trap.
Context: The CFTC’s 90-Day Review and the Settlement Test
The CFTC proposed a 90-day mandatory review for event contracts involving ‘gaming, terrorism, or other illegal activities’. The key word is ‘involve’. Under the proposal, any contract that touches a listed activity — even indirectly — would be subject to a Commission review before self-certification. The industry reads this as a blank check for regulatory overreach.
Hyperliquid and Multicoin’s letter makes two demands. First, the CFTC must publish a clear, functional definition of the ‘settlement test’ — the criteria that determine whether a contract’s payout depends on an external event. Second, the Commission must release the full reasoning behind any rejection decision, creating a public ledger of acceptable contract designs.
Logic remains; sentiment fades. The request is not about freedom. It is about predictability. Without a transparent settlement test, developers cannot model their contract logic against the regulator’s expectation. Without public reasoning, each rejection becomes a hidden precedent that only lawyers can parse.
Core: What the Settlement Test Means at the Code Level
I spent 2020 auditing liquidity pools. I learned that a single unchecked integer overflow can drain millions. The same precision applies here. The settlement test, in code terms, is a conditional payout function: if (oracle.report(event) == outcome) then transfer(payout). The CFTC wants to inspect that function before deployment. Fair enough. But if the criteria are opaque, the developer cannot know whether the oracle’s data format, the timeout window, or the dispute mechanism will trigger a review.
From my experience reverse-engineering 0x v2 order matching, I know that the gap between a whitepaper description and Solidity code is a minefield. A settlement test that says ‘payment must be determined solely by the event outcome’ sounds simple. In practice, every oracle update, every price feed deviation, every reentrancy guard introduces ambiguity. The Hyperliquid team understands this. Their letter asks for the test to be ‘functional’ — meaning the CFTC must define the exact on-chain operations that qualify as settlement.
Metadata is fragile; code is permanent. A public reasoning requirement would force the CFTC to publish the exact contract logic conditions that triggered a rejection. That creates a map: acceptable nodes, rejected edges. Builders can then design contracts that match the map. Without it, each new prediction market launch becomes a regulatory guessing game.
Multicoin’s involvement is strategic. As a venture firm with a portfolio across DeFi, they know that regulatory clarity reduces the cost of capital. But their letter does not ask for blanket approval. It asks for technical specificity. That is the correct approach. Trust no one; verify everything. Verification requires a known standard.
Contrarian: The Hidden Blind Spot — ‘Involve’ as a Trap Door
The industry celebrates the letter as a win for innovation. I see a deeper risk. The CFTC’s proposal uses the word ‘involve’ without definition. A sports prediction market ‘involves’ an athletic event. A political prediction market ‘involves’ an election. Both are currently legal in many jurisdictions. But if the CFTC interprets ‘involve’ to include any contract that references an event listed in its prohibited categories, the scope becomes infinite.
Consider a weather derivatives contract that uses a hurricane’s landfall as the event. If that hurricane causes damage classified as a ‘terrorist act’ by some government, does the contract now ‘involve’ terrorism? The letter does not address this semantic ambiguity. It focuses on process, not language. That is a blind spot.
Vulnerabilities hide in plain sight. The word ‘involve’ is a logic bomb. If the CFTC rejects a contract because it ‘involves’ a broadly defined activity, and if the public reasoning is opaque, the industry loses the ability to test edge cases. In my audits, I always look for the edge — the condition that flips a true to a false. The edge here is the definition of ‘involve’.
Moreover, the letter ignores state-level fragmentation. The CFTC can set federal rules, but New York, California, and Texas have their own gambling and securities laws. A prediction market that passes the CFTC settlement test could still be illegal in a state that classifies event contracts as gambling. The letter pushes for federal preemption but does not offer a concrete mechanism. That leaves a gap.
Impermanent loss is a feature, not a bug. In DeFi, liquidity providers accept impermanent loss as an expected cost. In regulation, jurisdictional fragmentation is the impermanent loss of compliance. It cannot be fully hedged.
Takeaway: The Next 90 Days Will Rewrite the Prediction Market Playbook
The CFTC’s response to these two requests will determine whether prediction markets remain a game of decentralized innovation or revert to a permissioned model run by traditional finance giants like Kalshi. If the Commission adopts a transparent settlement test and public reasoning, expect a wave of compliant contracts — each one a case study in code-level regulatory engineering. If not, the innovation will migrate offshore, and the $50 billion monthly volume will follow.
Frictionless execution, immutable errors. The CFTC has a choice: create a standard or watch the market define its own.