Disputed markets · Polymarket
Does a Polymarket deadline apply to the event or to the evidence?
Three things to check in a market with a deadline
- Does the deadline apply to the event, or to the evidence of it? “Sold by 31 May” and “shown to have sold by 31 May” are different bets.
- Can the named source report in time? If the source publishes weekly, monthly or only on business days, a late event may be impossible to prove before the market closes.
- What happens if the evidence arrives after the close? If the rules don’t say, someone will decide later, and it may not go the way the title suggests.
This Polymarket market left all three open. Strategy’s own filing showed a 32 BTC sale inside the window, published the day after the deadline. Polymarket resolved No. Read against the contract as listed, the Yes claim meets its terms.
The engine reads each claim three separate times. Agreement between the readings shows the reading was stable; it is not a ground of the finding or a measure of its correctness.
This page illustrates the method. It is not a challenge to the resolved outcome, and it is not a neutral resolution of the market.
The rule as listed
This market will resolve to “Yes” if MicroStrategy sells any of its Bitcoin by 11:59 PM ET on the date specified in the title. Otherwise, this market will resolve to “No”. The primary resolution source for this market will be information from MSTR and on-chain data, however a consensus of credible reporting will also be used.
What the wording addresses
- The event: a sale of any of Strategy’s bitcoin.
- The deadline: 11:59 PM ET on the date in the title, 31 May 2026.
- The source: information from Strategy (MSTR) and on-chain data, with a consensus of credible reporting also used.
What the wording leaves open
- Whether the deadline applies to the date of the sale or the date it is disclosed.
- That the named source reports weekly, so a sale in the final week could only be disclosed after the deadline.
- How on-chain data would show a sale: a transfer to a custodian is not a sale, and Strategy does not confirm which wallets are its own.
The evidence at the time of the claim
- Strategy Form 8-K, filed 1 June 2026 (period of report 30 May): 32 BTC sold in the period 26–31 May, with bitcoin activity presented as of 31 May 2026, 4:00 PM ET.
- Strategy’s previous 8-K, 26 May 2026: no bitcoin purchased 18–25 May; holdings stated as of 25 May.
- A Polymarket “additional context” note dated 1 June 2026, after expiry: “Confirmation achieved outside of the market’s time frame does not qualify.”
Was the deadline realistic?
In practice, no one could have proved a final-week sale before the deadline. Strategy reports its bitcoin activity weekly, in a filing that covers the previous week. 31 May 2026 was a Sunday, so a sale in the last week of May could only be disclosed on Monday 1 June. The previous filing, on 26 May, covered activity up to 25 May. On-chain data showed movement, not a sale: analysts linked wallets they attribute to Strategy to transfers to Coinbase Prime days before the filing, but a transfer to a custodian is not a sale. Credible reporting could only repeat a disclosure.
Under a rule that the evidence must be public before the market closes, the market’s real cut-off was about 25 May, and a sale in the final week would still have resolved it No.
The record, condition by condition
Meets the contract terms assessed Three of three readings agreed; no review required.
| Record | Condition | Assessment | Basis |
|---|---|---|---|
| R1 | Strategy sold some of its bitcoin | Met | The 8-K, a named primary source, reports a sale of 32 BTC. |
| R2 | The sale occurred by 31 May 2026, 11:59 PM ET | Met | The same filing places the activity in the period ending 31 May, as of 4:00 PM ET that day, within the deadline. |
| R3 | Evidence of the sale was public before expiry | Outside the terms assessed | This requirement appears only in the note added on 1 June, after expiry. It is not in the contract as listed, and the assessment does not add rules. Referred for confirmation that no such term existed before expiry. |
The wording that would have settled it
A term such as this would settle the point: “Evidence of the sale must be publicly available before the market closes.” The listed contract had none. A rule check before listing would have flagged both gaps: the deadline does not say whether it applies to the sale or its disclosure, and the named source’s weekly reporting cannot show a final-week sale before the deadline. Polymarket’s weekly Strategy markets open on 17 November 2026 ask whether Strategy will announce selling bitcoin in a given week, which ties the market to the disclosure rather than the sale.
After the claim (not used in the assessment)
The final review was decided by UMA token holders, with 98.6% of voting power supporting No. On 3 July 2026 two traders sued Polymarket in the Supreme Court of the State of New York (index no. 158389/2026), alleging the platform added a confirmation-by-deadline requirement after the fact. The case is pending; this page takes no view on it.
Restated as it stood when the claim was made; later facts were not given to the assessment. Assessed under ASR Methodology 1.12. Generated by AI; it can make mistakes.
Related
- What can go wrong when a prediction market resolves?
- Padilla v Mederos: a result corrected after the market expired
Sources
- Polymarket, “MicroStrategy sells any Bitcoin by ___ ?” market page, rules and resolution (the May 31, 2026 market)
- Strategy Inc, Form 8-K filed 1 June 2026 (SEC EDGAR)
- Strategy Inc, Form 8-K filed 26 May 2026 (SEC EDGAR)
- The Block, 1 June 2026: Polymarket’s added context note
- CoinDesk, 1 June 2026: the dispute stage
- The Block: UMA vote upholds No (after the claim)
- CoinDesk, 4 June 2026: No for May, Yes for June (after the claim)
- The Block, 7 July 2026: the lawsuit (after the claim)
- BeInCrypto: wallet movements to Coinbase Prime before the filing
Sources are listed so the case can be checked. Quotations are kept short; the market rules are quoted as the contract assessed.