Loading prices…
🩸BEARISH

Polymarket Rules Strategy's 32-BTC Sale Counts for June

UMA token holders sided with the disclosure-date reading, but a handful of whales controlled 25x the Yes vote — sharpening the DeFi-governance critique the same week the contract settled.

Polymarket Rules Strategy's 32-BTC Sale Counts for June
Polymarket Rules Strategy's 32-BTC Sale Counts for June
Polymarket Rules Strategy's 32-BTC Sale Counts for June
Polymarket Rules Strategy's 32-BTC Sale Counts for June

Polymarket has resolved its disputed bitcoin-sale prediction markets by ruling the May 31 contract No and the June 30 contract Yes, following a vote by UMA token holders that hinged on whether Strategy's June 1 public disclosure date should override the actual sale window. The bet was triggered by Strategy's first bitcoin sale in more than three years — 32 BTC moved between May 26 and May 31 — disclosed in an SEC Form 8-K filed on June 1.

Yes-position bettors argued a plain reading of the resolution criteria made the sale a May event. UMA voters sided decisively with the disclosure-date framing, despite the explicit May 26–31 window in Strategy's filing.

Why it matters

The decision turned less on the merits and more on voter concentration. borntoolate.eth cast 3.11 million UMA voting weight for No; UMA contributor Kevin Chan added 1.53 million; several other wallets cleared 1 million each. The four largest No voters controlled nearly 7 million voting weight — more than 25 times the entire Yes side. Wallets affiliated with Risk Labs, the company behind UMA, also voted No.

For DeFi governance writ large, the optics are ugly: a small group of large holders swung a multi-million-dollar market outcome. Galaxy Research, which held significant May-contract exposure, pushed back on X, noting that Strategy's Form 8-K "explicitly stated that Strategy sold between May 26–31. A plain reading of the resolution criteria would suggest that the market should have resolved to YES, hence the controversy."

Market impact

The Mechanism is the story more than the 32 BTC. A prediction market that resolves on procedural grounds rather than the underlying event can still be profitable for whales — but it strains the "trustless resolution" pitch that drew capital to Polymarket in the first place. Watch for: any follow-on UMA governance proposals to tighten voter-distribution rules, and whether rival oracle systems start pulling volume from Polymarket contracts on ambiguous-criterion events.

Related tokens
$BTC $UMA

Frequently asked questions

  1. Why did Polymarket resolve the May contract as No?

    UMA token holders, who run Polymarket's dispute-resolution oracle, sided with the argument that the public disclosure date — June 1 — should determine resolution, not the May 26–31 window when the 32 BTC actually changed hands.

  2. How concentrated was the UMA vote?

    The four largest No voters controlled nearly 7 million UMA voting weight, more than 25 times the entire Yes side. borntoolate.eth cast 3.11 million, and Risk Labs-affiliated wallets also voted No.

  3. What did Galaxy Research argue about the resolution?

    Galaxy, which had significant exposure to the May contract, said Strategy's Form 8-K explicitly stated the sale occurred between May 26 and May 31, so a plain reading of the criteria should have produced a Yes resolution.

  4. How much bitcoin did Strategy actually sell?

    Strategy sold 32 BTC between May 26 and May 31, 2026 — its first bitcoin sale in more than three years — and disclosed the transaction in an SEC Form 8-K filed on June 1.

  5. Why does this matter for DeFi governance?

    The result shows that whale concentration in oracle voting can override the underlying event's plain reading, undermining the "democratized resolution" pitch that drew capital to Polymarket and similar prediction markets.

Source attribution
Aggregated from CoinDesk · Verified · Last refreshed 47d ago
Open original →