Strategy’s first disclosed BTC sale puts Polymarket’s May 31 market into UMA review
A June 1 8-K revealed 32 BTC sold in late May, leaving a $14.65M contract hinging on timing rules.
Strategy’s June 1 8-K disclosure that it sold 32 BTC for about $2.5 million between May 26 and May 31 has triggered a settlement dispute on Polymarket. The May 31 deadline contract is flagged “in review” at roughly 81% “Yes,” with UMA’s optimistic oracle expected to deliver the final call.
Key Takeaways
- Strategy disclosed in a June 1 8-K that it sold 32 BTC for about $2.5 million between May 26 and May 31.
- Polymarket’s “MicroStrategy sells any Bitcoin by ___?” markets resolve “Yes” if any sale occurred by 11:59 p.m. ET on the deadline, creating a May 31 dispute because the sale preceded the June 1 public filing.
- The May 31 contract was marked “in review” and priced around 81% “Yes,” with about $14.65 million in volume and roughly $24.7 million across the May 31, June 30, and Dec. 31 markets.
- UMA’s optimistic oracle is expected to determine the final outcome, with disputes typically reviewed over about two days.
Strategy’s June 1 8-K Triggers a Polymarket Settlement Fight
Strategy’s first publicly disclosed bitcoin sale has become a live test of how prediction markets settle when the underlying event and the public evidence arrive on different dates. In a June 1 8-K, the company disclosed it sold 32 BTC for about $2.5 million between May 26 and May 31.
That disclosure collided with Polymarket’s timestamp-based contract series, “MicroStrategy sells any Bitcoin by ___?”, where each market resolves “Yes” if Strategy sold any bitcoin by 11:59 p.m. ET on the specified deadline. The May 31 market is the flashpoint. It was flagged “in review” and traded around 81% “Yes,” with about $14.65 million in volume.
The stakes are not marginal. Across the May 31, June 30, and Dec. 31 deadlines, the contracts drew roughly $24.7 million in volume, and the May 31 leg is now effectively waiting on an oracle decision rather than price discovery.
Inside the May 31 Deadline Dispute: Sale Timing vs. Disclosure Timing
The dispute is less about whether Strategy sold bitcoin and more about which clock governs settlement. The “Yes” side points to the 8-K’s table presentation and on-chain timestamps, arguing the sale occurred before the deadline and is even framed in the filing “as of May 31, 2026, 4:00 p.m. Eastern Time,” which they treat as consistent with the May 31 cutoff.
The “No” side argues the opposite interpretation: no public information existed before the June 1 filing, which arrived after the May 31 deadline had passed, so the May 31 contract should not pay out even if the sale itself happened in late May.
Polymarket’s resolution framework heightens the ambiguity. The rules cite Strategy filings and on-chain data as primary sources, with a fallback to a “consensus of credible reporting.” When a market’s payout depends on whether “timing” means execution time or disclosure time, the risk shifts from the underlying event to the resolution framework itself.
How UMA’s Optimistic Oracle Decides ‘In Review’ Markets
Polymarket uses UMA’s optimistic oracle to resolve ambiguous outcomes. In practice, an outcome can be proposed and then challenged, with disputes typically reviewed over about a two-day period before a final determination.
That process matters here because the May 31 contract is already labeled “in review,” and the market is still actively priced. The oracle’s decision will effectively choose which evidence standard dominates for this contract: the late-May sale window reflected in the 8-K and on-chain data, or the June 1 disclosure timestamp that made the sale broadly knowable.
Signals to Watch for Strategy BTC sale triggers Polymarket dispute
UMA’s final resolution for the May 31 contract is the immediate catalyst, given the typical two-day review window. Traders will also be watching whether the “in review” label clears quickly and whether pricing converges from roughly 81% toward a clean 0% or 100% outcome.
Any additional Strategy filings or clarifications that further specify the May 26–May 31 sale timing could narrow the interpretation space without changing the underlying fact pattern. After the June 1 disclosure, the June 30 and Dec. 31 contracts repriced to near-certain “Yes” at about 99.9 cents versus 0.1 cents “No,” so post-resolution repricing and volume shifts in those later markets will show whether participants treat the oracle call as precedent-setting.
What This Dispute Signals About Oracle Risk in Event Markets
I see this as a high-stakes example of oracle risk where the payout hinges less on whether the event occurred and more on how the resolution framework interprets timing. Strategy’s sale is disclosed, but the May 31 contract is still a live question because the market is being asked to decide whether “by May 31” means on-chain execution or public disclosure.
The threshold that matters is whether UMA’s final call aligns with how traders intuitively priced the series after June 1, when the June 30 and Dec. 31 markets snapped to near-100% “Yes” even as May 31 stayed contested. If that alignment holds, the setup starts to look structural rather than narrative-driven, because it tells participants which clock Polymarket effectively trades on when filings lag execution.
