Why
Three events, eight days, one axis. Korea's communications standards commission classified Polymarket as criminal gambling and blocked access. Six days later a CFTC-designated venue became the exclusive regulated partner of a large US brokerage network. The day after that, a US company put Apple and Nvidia shares on a public chain — and sold them only to people outside the US. Put the three in one table and the product column barely changes while the verdict column changes completely.
What is missing is not legal research, it is a box in the design document. Every architecture doc in this project has boxes for data model, settlement, oracle and failure modes. None has a box that says which jurisdiction this is legal in and what specifically makes it so. That absence is why the question keeps arriving as news rather than as a constraint — and a constraint that arrives as news arrives too late to design around.
The regulator did the hard half already. The stated grounds — a winner-take-all payout, an event the user cannot control, direct retail access — are not vague policy language. They are three product properties, each of which a design can move. Nobody has published that translation, which makes it available work rather than a summary of someone else's.
How it works
The three events, side by side
| Date | Event | Verdict on the activity | What actually differed |
|---|---|---|---|
| 2026-08-18 | Korea blocks access to Polymarket | Criminal gambling | Payout shape, event type, retail access — no licence available |
| 2026-08-24 | Gemini Titan becomes Apex Fintech's exclusive venue | A brokerage product line | A CFTC designation, obtained in December 2025 |
| 2026-08-25 | Coinbase lists tokenized equities on Base | Sellable, but not to US persons | The buyer's residence, nothing else |
The grounds, turned into levers
| Stated ground | The design lever underneath it | What moving it costs |
|---|---|---|
| Winner-take-all payout | Payout curve — binary versus scalar or continuous settlement | A continuous payout is a different product, and possibly a less useful one |
| User cannot control the event | Subject matter — exogenous events versus outcomes tied to the user's own action or skill | Narrows the market catalogue sharply |
| Direct retail access | Access path — retail direct versus intermediated or institution-only | Changes the business model, not the code |
Reading the second table is the whole exercise. Each lever is movable, none is free, and the combination decides which jurisdiction the product can stand in. A design that has not chosen a position on all three has, in effect, chosen the position that was blocked.
Why the December document needs two branches, not one
The legislative date is a date, not an outcome. Meanwhile the supervisory track proceeds regardless: implementing rules for the stablecoin statute are already being written, and the 2026 Jackson Hole symposium's announced theme puts roughly a hundred and twenty central bankers from seventy countries on payments and financial innovation for three days. Rules arrive without legislation, and the intensity of lobbying is not the probability of passage. So the document needs a legislation branch and a rulemaking-only branch — and the honest expectation is that the two differ more in timing than in substance.