Polymarket is facing a major resolution dispute after Strategy disclosed that it sold 32 BTC before May 31, while the relevant prediction market moved toward a “No” outcome because the sale was not publicly confirmed until June 1. The controversy turns on a narrow but consequential question: whether a market should resolve based on when an event happened or when it became verifiable.
Strategy’s June 1 SEC filing states that the company sold 32 BTC between May 26 and May 31 for about $2.5 million, at an average net price of $77,135 per coin. The filing also says proceeds are expected to fund distributions on preferred stock, leaving Strategy with 843,706 BTC as of May 31 at 4:00 p.m. Eastern Time. For “Yes” bettors, that filing appears to confirm that the sale occurred inside the market window.
A Timing Dispute Becomes a Market-Integrity Test
The affected Polymarket contract stated that it would resolve to “Yes” if MicroStrategy sold any of its Bitcoin by 11:59 p.m. ET on the date specified in the title, with information from MSTR and on-chain data as primary sources. The same page displayed a “No” outcome proposal, dispute status and final review, showing that the settlement process itself became the center of the trade.
The platform’s clarification framed the issue differently. It said that no information from MSTR, on-chain data or a consensus of credible sources confirmed the sale within the market’s timeframe, and that confirmation outside the timeframe did not qualify. That interpretation made disclosure timing the practical resolution trigger, not only the date on which Strategy executed the sale.
That distinction is what angered “Yes” holders. Their argument is straightforward: the market asked whether Strategy sold Bitcoin by May 31, and Strategy later disclosed that it did. They say a post-close confirmation rule changed the economic meaning of the contract after traders had already priced the risk.
The stakes were large enough to matter beyond one market. More than $80 million had been wagered on whether Strategy would sell Bitcoin by May 31, and the odds collapsed after the “No” interpretation gained force. A market that was supposed to price a corporate treasury event became a test of Polymarket’s rule architecture.
Prediction Markets Need Cleaner Evidence Standards
The dispute exposes a persistent weakness in prediction-market design. Some events are factual before they are public, especially corporate transactions that occur before required filings are released. Without explicit wording, traders can reasonably disagree over whether the decisive standard is occurrence, announcement or confirmation.
Polymarket’s wording relied on official company information and on-chain data, but the event itself was confirmed through an SEC filing after the May 31 deadline. That created a gap between the execution date and the evidence date. In high-volume markets, that gap can redistribute millions of dollars based on procedure rather than the underlying fact.
The episode also arrives against a regulatory backdrop that already puts Polymarket under scrutiny. In January 2022, the CFTC ordered Blockratize, doing business as Polymarket.com, to pay a $1.4 million civil monetary penalty and wind down noncompliant markets. Resolution disputes can therefore become compliance problems as well as user-trust problems.
The lesson is practical: contract wording must be read with the same discipline as a derivatives term sheet. Markets tied to filings, announcements or corporate actions need precise language on timing, including whether later evidence can validate an event that occurred before the deadline.
For Polymarket and similar platforms, the operational fix is equally clear. Resolution criteria should state in advance whether the trigger is the event date, the announcement date or the confirmation date, and those criteria should remain fixed for the life of the market.
The Strategy dispute may ultimately be remembered less for the 32 BTC sale than for what it revealed about market plumbing. Prediction markets cannot scale institutional trust if verifiable events become post-settlement arguments over wording, evidence windows and oracle discretion.
