Bettors are embroiled in a roughly $79 million showdown over a three-word ambiguity: did MicroStrategy (MSTR) sell bitcoin “by 11:59 PM ET” on May 31? The Polymarket contract at the center of the dispute asked a simple yes-or-no: had MicroStrategy sold any bitcoin by that deadline? MicroStrategy’s 8-K, filed June 1, disclosed that the company executed trades totaling 32 BTC “during period May 26, 2026 to May 31, 2026” and listed the activity “as of May 31, 2026, 4:00 p.m. Eastern Time.” That places the sales inside the calendar window, but the public filing — the confirmation many traders rely on — didn’t appear until after the deadline had passed. Which matters: the date the trades occurred or the date they were disclosed? That single ambiguity turned the market into a three-way fight mapped onto UMA’s voting options: - The “event-based” camp (vote P2 = Yes) says the contract resolves on the underlying event. MicroStrategy’s own disclosure dates the activity to May 31, so the sale happened inside the window and the market should pay out Yes. - The “announcement-based” camp (vote P1 = No) argues the contract effectively resolves on confirmed information available by the cutoff. Because no on-chain data, credible reporting, or MicroStrategy filing confirming the sale existed before 11:59 PM ET on May 31, the market should settle No. - A smaller “rules-too-vague” group invoked P4 (Too Early), saying the contract’s language was unclear — it refers both to “by” and to “on the date specified in the title” — and that the market should have stayed open until MicroStrategy’s imminent 8-K was published. Polymarket’s dispute thread and UMA’s Discord saw hours of back-and-forth. Supporters of the Yes reading note the contract names “information from MSTR” as the primary source and point to the explicit “as of May 31, 2026, 4:00 p.m. ET” timestamp in MicroStrategy’s filing. Opponents counter that allowing post-deadline disclosures to retroactively determine outcomes would let traders keep markets unresolved until a favorable confirmation appears — undermining integrity and turning markets into bets on filing cadence rather than events. Polymarket itself added context favoring the No outcome, stating that no MicroStrategy disclosure, on-chain evidence, or reliable reporting confirmed a sale within the market’s timeframe and that “confirmation achieved outside of the market’s time frame does not qualify.” Markets reacted fast: the May 31 contract plunged from about 81% Yes during the dispute to under 1% Yes after the platform’s guidance. But the final say isn’t Polymarket’s — it’s UMA token holders who vote to resolve UMA-based markets. The two systems have split before: in 2024 UMA ruled one way on a DJT memecoin question while Polymarket chose a different path, ultimately refunding some holders. For this MicroStrategy market, Polymarket and UMA currently appear aligned, and the trade referenced in the 8-K is effectively trading for less than a penny. Why this matters beyond one contract: the episode highlights a core fragility in event markets — sloppy phrasing around deadlines and “by” versus “confirmed by” can turn otherwise straightforward questions into multimillion-dollar governance battles. As prediction markets and on-chain oracles grow in size and significance, clearer rule drafting and pre-agreed confirmation sources will be essential to avoid repeated, costly disputes. Read more AI-generated news on: undefined/news