Polymarket Resolves Bitcoin Sale Timing Dispute Between May, June Contracts
UMA token holders voted to resolve a Polymarket prediction contract dispute over when Strategy's bitcoin sale occurred, ruling the June 1 disclosure applies to the June contract despite the sale happening in late May. The decision clarifies how Polymarket handles disclosure timing for event-based contracts.
Key Takeaways
- 1## The Dispute Polymarket prediction contracts tied to Strategy's bitcoin holdings split over the timing of a recent cryptocurrency sale.
- 2Strategy disclosed a bitcoin divestment on June 1, but stated the sale executed during the final week of May.
- 3Holders of Polymarket's May contract argued the disclosure timing meant the sale should count as a May event; June contract holders contended the June 1 disclosure date was the relevant data point.
- 4## How UMA Resolved It UMA token holders voted to rule that Strategy's June 1 disclosure counted for the June contract, not the May contract.
- 5The decision effectively set the May contract to resolve "No" and the June contract to "Yes," establishing that for Polymarket's purposes, the date of public disclosure—rather than the date of the underlying transaction—governs contract resolution when the two dates differ.
The Dispute
Polymarket prediction contracts tied to Strategy's bitcoin holdings split over the timing of a recent cryptocurrency sale. Strategy disclosed a bitcoin divestment on June 1, but stated the sale executed during the final week of May. Holders of Polymarket's May contract argued the disclosure timing meant the sale should count as a May event; June contract holders contended the June 1 disclosure date was the relevant data point.
How UMA Resolved It
UMA token holders voted to rule that Strategy's June 1 disclosure counted for the June contract, not the May contract. The decision effectively set the May contract to resolve "No" and the June contract to "Yes," establishing that for Polymarket's purposes, the date of public disclosure—rather than the date of the underlying transaction—governs contract resolution when the two dates differ. UMA's oracle mechanism allows token-holder consensus to settle disputed market outcomes when contract language is ambiguous.
Implications for Event Markets
The ruling sets a precedent for how Polymarket and similar prediction markets interpret event timing when disclosure dates lag transaction dates. Traders and market creators will need to pay closer attention to whether prediction contracts are keyed to transaction date, disclosure date, or announcement date—distinctions that can determine payouts when those dates straddle contract boundaries.
Why It Matters
For Traders
When trading event-based prediction contracts, verify whether the contract specifies transaction date or disclosure date; ambiguity can swing payouts between adjacent contract periods.
For Investors
UMA's oracle resolution process is working as designed for disputed outcomes, but market creators should tighten contract language to prevent similar disputes in the future.
For Builders
Prediction market platforms need clearer event definition standards in contract templates to reduce oracle disputes and improve user confidence in settlement.
