Polymarket $60M Dispute Heads to UMA Vote

Digital interface displaying Bitcoin icon, market charts, and voting checkboxes on a dark blue background with data lines.

Polymarket’s $60 Million Bitcoin Sale Market Disputed Twice – UMA Token Vote to Decide Outcome

Key Takeaways

A Polymarket contract with more than $60 million in trading volume on whether MicroStrategy sold Bitcoin by May 31, 2026 has been disputed twice.
The dispute has been escalated to a token-weighted vote by UMA tokenholders under the optimistic oracle system.
The trigger is an 8-K filing disclosing that 32 BTC were sold between May 26 and May 31 at an average net price of $77,135.
The contract currently trades at 12c Yes and 89c No, with settlement hinging on how the timeframe is interpreted.

Polymarket Contract on Bitcoin Sale Escalates to UMA Tokenholders

A high-volume prediction market on Polymarket is now awaiting resolution through a token-holder vote after two proposed outcomes were challenged. The contract asked whether MicroStrategy sold any Bitcoin by May 31, 2026 and attracted more than $60 million in trading volume.

Two proposed “No” resolutions were disputed, automatically escalating the case to UMA’s optimistic oracle system. Under this structure, disputes can be challenged twice before being sent to a vote among UMA tokenholders. Voting power is determined by token weight, and the result of that vote determines the final payout.

The dispute centers on an 8-K filing released on June 1. The filing disclosed that 32 BTC were sold between May 26 and May 31 at an average net price of $77,135. The sales occurred before the contract’s cutoff time of 11:59 PM ET on May 31. The filing itself was published after the market’s timeframe had ended.

At the time of writing, the market is priced at 12c for Yes and 89c for No, indicating that traders currently assign a higher probability to a No resolution.

Interpretation of the Timeframe Drives the Dispute

The central issue is how the contract’s timeframe should be interpreted. Yes-side traders argue that the question refers to whether sales took place during May, regardless of when they were publicly disclosed. They point to the 8-K statement that the transactions occurred between May 26 and May 31.

Polymarket posted a bulletin to UMA voters stating that no information from MicroStrategy, on-chain data, or credible reporting confirmed within the market’s timeframe that the company sold Bitcoin during that period. The notice added that confirmation achieved outside of the market’s timeframe does not qualify.

Because the 8-K was released on June 1, after the cutoff, the dispute turns on whether execution of the sale within May is sufficient, or whether public confirmation was required before the deadline.

The financial stakes are significant for individual traders. One holder, identified under the pseudonym “Surprised-Legacy,” placed a $19,610 wager at roughly 11c. If the contract resolves to Yes, that position would pay out approximately $200,000.

UMA’s Optimistic Oracle Under Scrutiny

The case has renewed attention on UMA’s token-voting oracle model. In this system, contested resolutions are ultimately decided by tokenholders rather than by a centralized authority or court.

A Wall Street Journal investigation published in May examined voting patterns in disputed Polymarket markets. According to the report, in most disputed markets more than half of UMA votes came from the ten largest wallets. At least 60 percent of active UMA voters could be linked to live Polymarket accounts. Roughly one in five disputes included at least one voter with a financial stake in the contract being decided.

Polymarket has recorded more than 1,150 disputed markets in 2026, already exceeding its full-year total for 2025. The current Bitcoin sale contract is described as the highest-dollar live test of the system since a $237 million market last year related to Ukrainian President Volodymyr Zelenskyy.

Under the existing structure, Polymarket cannot override the result of the UMA vote. The token-weighted outcome is binding for settlement.

Alternative Settlement Models in Prediction Markets

The dispute also highlights differences in how prediction markets handle settlement.

Hyperliquid’s HIP-4 outcome markets, which went live on mainnet on May 2, use a different approach. According to the source material, settlement is determined by the chain’s validator set running automated newsfeed software. There is no token-vote backstop and no dispute window. Each binary contract resolves to 1 or 0 based on a pre-specified data source.

Kalshi operates under a separate model as an exchange-cleared central counterparty through Kalshi Klear LLC, which has been registered as a derivatives clearing organization with the Commodity Futures Trading Commission since August 2024. Disputes are handled under exchange rules filed with a federal regulator.

Polymarket’s U.S. arm is registered as a designated contract market with the CFTC. However, the international book, where the MicroStrategy market is listed, settles in USDC on Polygon using UMA’s oracle system.

Related Contracts and Current Voting Timeline

The outcome of the disputed contract contrasts with two related markets covering June 30 and December 31 deadlines. Those contracts resolved to Yes without dispute.

For the May contract, the UMA voting window runs for roughly two days. The entire $60 million in trading volume now depends on whether voters interpret the question as requiring public disclosure within May or simply the execution of a sale within that month.

Until the vote concludes, funds remain tied to the pending resolution.

Our Assessment

The $60 million Polymarket dispute demonstrates how settlement mechanics can materially affect high-volume prediction markets. The outcome will be determined by UMA tokenholders under a token-weighted voting system after two challenges to a proposed resolution. The decision hinges on the interpretation of the contract’s timeframe in relation to an 8-K filing that disclosed Bitcoin sales executed before May 31 but published on June 1. The case also highlights structural differences between token-vote oracles, validator-based automated systems, and regulated exchange clearing models used across prediction platforms.