Call of Duty: G2 Minnesota vs Cloud9 New York (BO5) - Call of Duty League Stage 3 Minor Playoffs
Volume:
$95,958
Markets
Outcome
Chance %
Price
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
Trade
Description
G2 Minnesota and Cloud9 New York compete in a Best-of-5 match during the Call of Duty League Stage 3 Minor Playoffs, originally scheduled for April 24, 2026 at 6:00 PM EDT. The match outcome and individual game results will determine resolution across multiple derivative markets (game winners, game totals, and handicaps). All markets reference the same underlying real-world event with consistent team identification and completion criteria.
Unified Resolution Criteria (Consistent across platforms)
Both Polymarket and Kalshi resolve based on the actual match outcome between G2 Minnesota and Cloud9 New York, with Liquipedia as the primary resolution source and consistent handling of cancellations, delays beyond 7 days, and incomplete matches.
Primary resolution logic:
Official information from https://liquipedia.net/callofduty/Main_Page, with credible reporting and video evidence as fallback if results not published within 2 hours of event conclusion.
Core resolution logic:
Match winner resolves to the team that wins the best-of-5 series against the opponent.
Individual game winners resolve based on the team that wins that specific game, provided the game is completed.
Games total (O/U 3.5 and O/U 4.5) resolve based on the total number of games played, including forfeits, disqualifications, walkovers, and defaults, provided the match is completed.
Game handicaps (MIN -1.5 and MIN -2.5) resolve based on the game differential, with MIN winning if they win 2+ or 3+ more games respectively.
If the match is canceled, not played at all, delayed beyond 7 days without play beginning, or ends in a tie, all markets resolve 50-50.
If the match begins but is not completed, individual game markets resolve 50-50 unless that specific game is concluded with a winner; match winner and handicap markets resolve 50-50 unless one team wins via opponent forfeiture/disqualification/walkover (in which case the winning team resolves YES for match winner only); games total markets resolve 50-50 unless the match ends due to clinching game forfeiture (which counts as completed).
Edge cases & Clarifications:
Incomplete Match with Forfeiture: If the match begins but is not completed and one team wins due to opponent forfeiture, disqualification, or walkover, the match winner market resolves to the winning team, but games total and handicap markets resolve 50-50 unless the forfeiture occurs on the clinching game (which counts as a completed match).
Clinching Game Forfeiture: If the match ends due to the clinching game being forfeited, this counts as a completed match and games total and handicap markets resolve based on the final game count and differential.
Individual Game Completion: If the match begins but is not completed, individual game markets (Game 1, 2, 3, 4 winners) resolve based on the completed game if a winner is determined; if the game is not completed, the market resolves 50-50.
Source Fallback Timeline: If Liquipedia has not published final results within 2 hours after event conclusion, credible reporting and video evidence may be used as resolution source.
Timing:
Resolution occurs upon completion of the match and official publication of results on Liquipedia, or within 2 hours thereafter via credible reporting if Liquipedia is delayed.
Our PredictionHero Resolution Divergence Alerts (RDA) are there to help users identify potential differences across platforms. They do not replace or supersede the official rules and description of any prediction market. Users are solely responsible for reviewing and understanding the applicable rules and resolution criteria before placing any trade or bet. If you notice a potential inconsistency, discrepancy, or error in an alert, please report it to our team so we can review and improve the accuracy of our data.
Follow the signals, not the noise
Get insights on market conviction, notable shifts, and what the data is quietly signaling.