Strategy (MSTR) sold bitcoin in late May, and told the market in June. Here's how Polymarket bettors are fighting over when it counts.
A $79 million Polymarket market is split over whether Strategy's 32 BTC sale counts by May 31 or only once disclosed on June 1.
Intelligence analysis by GPT-5.4 Mini
Polymarket bettors are arguing over whether a bitcoin sale should count when it happened or when it was publicly disclosed. Strategy's filing says the 32 BTC sale happened during May 26-31, but the disclosure arrived after the deadline, creating a high-stakes dispute over contract wording.
A betting market asked a simple question: did Strategy sell bitcoin before the end of May?
The trouble is that Strategy says it sold some bitcoin during the last days of May, but people only learned that on June 1. That is like finding out after a race ends that one runner had crossed the line earlier, but the photo was shown later.
Some people think the sale counts because it really happened in time. Others think it does not count because the proof arrived too late. Now a separate voting group has to decide which reading wins.
Analysis
What happened
Strategy’s Polymarket market asked whether the company sold any bitcoin by May 31. The dispute began because Strategy’s filing says it sold 32 BTC between May 26 and May 31, but that filing was not published until June 1.
Why bettors split
One side reads the contract as event-based: if the sale happened inside the window, the answer should be Yes. They point to Strategy’s own filing, which dates the activity as of May 31 and identifies Strategy as the primary source.
The other side treats the market as announcement-based: if the sale was not confirmed by the deadline, then the answer should be No. That camp argues the market should only use information that was knowable before the cutoff, and that allowing later disclosure to change the result would weaken deadline integrity.
The third argument
A smaller group says the wording was too vague to resolve cleanly at all. They argue the rules were not drafted clearly enough about whether the sale had to occur by the deadline or be confirmed by then, and that the market should have stayed open until the filing appeared.
How it stands now
Polymarket has since backed the No interpretation, saying no MSTR information, on-chain data, or credible reporting confirmed a sale within the timeframe and that confirmation after the window does not count. Traders moved with that view, and the May 31 contract dropped from 81% Yes during the dispute to under 1%.
Even so, the final call belongs to UMA token holders, not Polymarket alone. The article notes the two have disagreed before, including a 2024 dispute over a Barron Trump-related market, so the outcome still depends on how the oracle vote lands.
Key points
- A $79 million Polymarket market is centered on Strategy's 32 BTC sale and whether it counts by May 31.
- Strategy says the sale happened between May 26 and May 31, but the filing was published on June 1.
- One camp says the event itself matters; another says only information confirmed by the deadline should count.
- Polymarket has backed the No interpretation, but UMA token holders make the final resolution.
- The dispute shows how prediction markets can turn on timing, wording, and source rules.
If the market is resolved using Strategy’s own filing as the primary source, the contract has a clear event-based outcome tied to the sale itself. That would reinforce the idea that prediction markets can settle on the underlying facts, even when disclosure comes later.
If the market is treated as requiring confirmation before the deadline, traders who priced in the late disclosure may lose despite the sale having occurred inside the window. The episode also shows that unclear contract wording can leave large markets vulnerable to disputes over timing and interpretation.
