Polymarket Sued After ‘No’ Call on Strategy’s BTC Sale Triggers Oracle Backlash

Two traders say Polymarket retroactively changed rules to deny a winning “Yes” on Strategy’s 32 BTC sale. UMA voters upheld a “No.” The case tests oracle governance and market trust.

Bitcoin
Cryptocurrency
Regulations
Economy
Because Bitcoin
Because Bitcoin

Because Bitcoin

July 7, 2026

A fight over when proof counts—not just when an event occurs—is dragging prediction markets back into court.

Two Polymarket users, William Wood and Thomas Bush, sued in New York Supreme Court on July 3, alleging the platform wrongly settled a market on whether Strategy would sell any Bitcoin by May 31 as “No.” They named CEO Shayne Coplan and CMO Matthew Modabber and seek the $1-per-share payout on their “Yes” positions, plus damages, legal fees, and relief under claims including breach of contract, breach of the implied covenant of good faith and fair dealing, unjust enrichment (in the alternative), deceptive practices, and false advertising.

The dispute centers on evidence timing. Strategy—led by Michael Saylor—disclosed in a June 1 SEC filing that it sold 32 BTC between May 26 and May 31, its first sale since 2022. Polymarket, however, resolved the market “No” after UMA voters—the oracle used for disputes—determined that public confirmation arrived outside the market’s window. Polymarket appended guidance stating that confirmations posted after the cutoff would not qualify. Plaintiffs argue that Strategy’s own disclosures were designated as the primary source in the rules and that injecting a confirmation-deadline standard after the fact flipped a winning “Yes” into a loss. In their telling, a market that refuses to pay on a clearly proven event is prioritizing control over outcome rather than truth.

One plaintiff amplified the claim on X, saying Polymarket “scammed” him for roughly $500,000, and that 1,868 traders collectively lost about $6.5 million tied to the ruling, adding they are taking the platform to court.

The case lands as Strategy expands its selling activity. The company has outlined plans to sell up to $1.25 billion more Bitcoin to fund dividends and, this week, sold approximately $216 million in BTC under its “BTC monetization program.”

The crux: confirmation vs. occurrence This is a classic oracle design pitfall. Traders price the probability of an event occurring by a deadline. Oracles often require a verifiable record to confirm it. When those clocks diverge—event happens by T, evidence posts at T+1—governance becomes the tiebreaker. If market pages do not lock an immutable hierarchy of sources and acceptable timestamps (e.g., SEC EDGAR acceptance time), discretionary interpretation creeps in. That is where trust erodes.

What worries me more than this single outcome is incentive alignment. Investigations this year reported that a small set of large wallets can sway many dispute votes, and that numerous UMA voters also hold positions in the very markets they adjudicate. Even if the voting process is technically sound, the optics are rough. A visible conflict of interest invites regulatory and legal heat—especially now that Polymarket’s U.S. arm operates as a CFTC-registered exchange.

Business impact and fixes that actually matter Polymarket has logged over 1,150 disputed markets in 2026, already exceeding last year’s total. The Strategy fight is its biggest controversy since a $237 million market last year over whether Ukraine’s president wore a suit. Yet growth momentum persists: the company has reportedly drawn close to $2 billion from NYSE parent ICE, was last valued at $9 billion, and in April was said to be seeking $400 million at a $15 billion valuation. Burwick Law, which brought this case, says it is evaluating similar claims. Polymarket has not publicly responded.

If the industry wants institutional users to view prediction markets as price-discovery tools rather than gambling venues, three guardrails are non-negotiable: - Evidence windows must be codified pre-launch: event-time vs. proof-time, with explicit rules for filings posted after the cutoff but covering the in-window period. - Source priority must be deterministic and timestamp-aware (e.g., EDGAR acceptance time, not press release time). - Oracle governance should mitigate conflicts: exclude voters with market exposure, disclose voter stakes, or separate “jury pools” from market participants.

None of that is exotic. It is product discipline. Without it, traders will price in oracle risk, spreads will widen, and capital will migrate to venues with cleaner resolution mechanics.

What to watch - Whether the court treats post-hoc clarification as a material rule change. - UMA’s community response on voter conflicts and any move to restrict conflicted voting. - Polymarket’s willingness to harden source/timestamp rules across markets.

Strategy’s 32 BTC sale is small. The precedent on when proof counts is not. In prediction markets, resolution credibility is the asset.