A dispute has erupted on the prediction platform Polymarket over whether MicroStrategy sold Bitcoin by May 31 [1].
The conflict highlights the tension between on-chain data and official corporate filings in decentralized betting markets, where millions of dollars depend on the precise definition of a "sale."
According to an 8-K filing disclosed on June 1, MicroStrategy conducted a Bitcoin sale between May 26 and May 31 [4]. This disclosure has created a rift among bettors regarding the outcome of a specific contract. Some users argue that the on-chain transaction date should determine the result, while others maintain that the official filing date is the only valid trigger [1], [4].
Reports on the total amount of money at stake vary. Some sources said that $80 million was wagered on whether the company would sell by the May 31 deadline [1], [2]. Other reports place the amount of the dispute at $50 million [3] or as low as $14 million [4].
Market sentiment has remained volatile as users attempt to reconcile the data. One report said that the sale of 32 BTC moved the market into "No" territory [7]. However, other data indicates the May 31 contract was sitting at 81% "Yes" [4]. This discrepancy underscores the chaos surrounding the resolution of the bet.
Additional markets on the platform have also tracked the company's behavior, with some odds placing the likelihood of MicroStrategy selling Bitcoin this year at 82% [2].
The resolution of the May 31 contract now depends on how Polymarket interprets its own rules regarding the timing of corporate disclosures versus the actual movement of assets on the blockchain.
“A dispute has erupted on the prediction platform Polymarket over whether MicroStrategy sold Bitcoin by May 31.”
This dispute illustrates a fundamental conflict in the 'oracle' problem of prediction markets: the gap between when an event happens on a blockchain and when it is legally recognized by a corporation. If the platform favors filing dates over on-chain evidence, it may discourage the use of real-time data in future contracts. Conversely, favoring on-chain data could lead to volatility based on unconfirmed movements that companies may not officially acknowledge for days.
