Polymarket Resolves Disputed Bitcoin-Sale Markets: May Contract Ruled No, June Contract Ruled Yes After UMA Vote
Table of Contents
You might want to know
1. Should the timing that determines a prediction market’s outcome be the date a transaction occurred or the date it was publicly disclosed?
2. What are the governance and decentralization implications when a small number of large token holders determine dispute outcomes?
Main Topic
This article summarizes a recent resolution on Polymarket relating to disputed prediction markets about whether Strategy — an entity holding bitcoin — had sold bitcoin by specified deadlines. Two separate contracts were in question: one that asked whether Strategy would sell bitcoin by May 31, and another that asked whether it would sell by June 30. The dispute followed Strategy’s disclosure that it sold 32 bitcoin in a window spanning May 26 to May 31, with the public filing announcing the sale made on June 1. UMA token holders, who serve as the dispute-resolution layer within Polymarket’s oracle framework, voted on how the markets should resolve.
At issue was how to interpret the market’s resolution criteria. One interpretation favored the physical timing of the sale — because the transaction took place between May 26 and May 31, it therefore met the May 31 deadline. The alternative interpretation prioritized the date of public disclosure, arguing that an event should only count for a market if it was publicly known by the market’s cutoff. UMA voters adopted the latter view: the sale was treated as relevant to June because the disclosure occurred on June 1. As a result, the May 31 contract resolved to No, and the June 30 contract resolved to Yes.
The ruling produced immediate and strong reactions. Many bettors who purchased Yes on the May market lost their positions despite the subsequent filing showing the sale happened during the final week of May. Those traders argued that the plain facts — the sale dates listed in the filing — should determine the market outcome. Conversely, others stressed that prediction markets rely on publicly available information; if a sale is not disclosed before a cutoff, allowing it to retroactively determine the resolution could undermine clarity and enforceability of market rules.
The voting results revealed a concentration of governance power. A small number of large UMA token holders cast decisive votes in favor of No for the May contract. The single largest recorded vote came from an address identified as borntoolate.eth, which cast approximately 3.11 million voting weight for No. Other substantial No votes included an UMA contributor (recorded with about 1.53 million voting weight) and multiple wallets each contributing more than one million weight. Collectively, the four largest No voters controlled nearly 7 million voting weight, an amount that dramatically exceeded the aggregated Yes votes and effectively determined the outcome.
Several wallets linked to Risk Labs, the organization behind UMA, also voted No, in addition to other prominent participants within the UMA ecosystem. The influence of these large voters reignited concerns about the concentration of authority in decentralized finance governance — a core philosophical tension between the ideals of decentralization and the realities of token-weighted voting systems.
Some market participants and observers pushed back on the decision. For instance, a research group that had meaningful exposure to the May contract publicly criticized the outcome, emphasizing that Strategy’s SEC filing explicitly stated the sale occurred between May 26 and May 31. From this perspective, the resolution should have favored Yes for the May market because the criterion of whether the sale occurred by the deadline was, in their view, unambiguous. The disagreement highlights a gap between textual event timing and the practical mechanics of market resolution when public disclosure lags transactional reality.
The controversy underscores several broader themes in prediction markets, oracle governance, and decentralized protocols. First, the matter highlights the need for unambiguous resolution language in markets — when a market’s wording leaves room for interpretation about whether the material fact is the actual event date or the disclosure date, disputes are likely. Second, it illuminates the role of dispute resolution systems and their reliance on token-holder adjudication; the system operates under the assumption that token holders will act as neutral arbiters, but concentrated holdings can distort this mechanism. Third, it raises reputational and operational questions for projects that build dispute-resolution processes into protocol design: if settlement outcomes can hinge on a handful of wallets, users and counterparties may perceive higher counterparty or governance risk.
Finally, this episode contributes to ongoing dialogue within crypto communities about how to balance timely, factual resolution with fairness and predictability. Markets need clear, enforceable rules that align participants’ expectations, while governance mechanisms need structural safeguards to prevent outsized influence by a small cohort of token holders. Some possible mitigations include more precise contract language, escalation processes that consider both event dates and disclosure contexts, and governance reforms such as quadratic voting or identity-based voting to dilute token-weight concentration.
In short, the Polymarket decision to resolve May as No and June as Yes after an UMA token-holder vote reflected a prioritization of public disclosure timing over underlying transaction timing, and the decision-making process exposed how token-weighted governance can deliver concentrated influence over dispute outcomes.
Key Insights Table
| Aspect | Description |
|---|---|
| Disputed Event | Whether Strategy's sale of 32 BTC between May 26–31 counted for a May 31 prediction market cutoff. |
| Resolution Ruling | UMA voters ruled the May contract No and the June contract Yes, prioritizing disclosure date. |
| Deciding Factor | Public disclosure on June 1 determined outcome, not the transaction dates in late May. |
| Governance Dynamic | A handful of large UMA token holders cast votes that overwhelmingly influenced the result. |
| Stakeholder Reaction | Some bettors and analysts criticized the ruling; disputes about whether event timing or disclosure should govern persist. |
Afterwards...
Looking forward, this incident is likely to prompt market designers and governance communities to reassess how contracts define resolution criteria and how dispute-resolution power is distributed. Clearer contract language that specifies whether public disclosure is required or whether actual event timing suffices could reduce ambiguity. Additionally, governance reforms or procedural safeguards could be considered to limit outsized influence from a small number of token holders, preserving trust in decentralized dispute processes.
For market participants, the episode is a reminder to review resolution terms carefully and to consider counterparty and governance risk when engaging with token-weighted dispute systems. For protocol teams, it underscores the importance of robust governance models that align incentives, protect minority stakeholders, and maintain predictable outcomes for market users.
Ultimately, the Polymarket-UMA dispute serves as a case study in the trade-offs between factual clarity and procedural norms in decentralized markets — and it will likely influence how future markets are structured and how governance power is balanced.
