TOTAL VOLUME:

$134.2b

24H VOL:

$134,145,987

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,441,166,947

406,422

Markets across

30,383

events

MATCHED EVENTS:

2,688

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Insights
Indices
Tour
All
Trending
Breaking
New
Ending Soon
Politics
Sports
Crypto
Companies
Elections
Financials
Economics
Other
Entertainment
Science and Technology
Counter-Strike: M80 vs Voca (BO3) - ESL Challenger League North America Cup 1 Playoffs
kalshi
polymarket

Counter-Strike: M80 vs Voca (BO3) - ESL Challenger League North America Cup 1 Playoffs

Volume:
$34,205

M80

 - Kalshi

M80 - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Feb 23, 2026

Closed: Feb 23, 1:00 AM EST

kalshi

Kalshi

View
Join Kalshi and score $25 for your first trade.
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
kalshi

M80

View
100%
Yes 100¢No 0¢
—
N/A
$7,718
N/A
N/A
$5,933
Settled
Yes
kalshi

Voca

View
0%
Yes 0¢No 100¢
—
N/A
$13,964
N/A
N/A
$11,697
Settled
No
polymarket

Match Winner

100%
Yes 100¢No 0¢
—
N/A
$10,986
0%
N/A
N/A
N/A
polymarket

Map 2 Winner

100%
Yes 100¢No 0¢
—
N/A
$1,040
0%
N/A
N/A
N/A
polymarket

Map 1 Winner

100%
Yes 100¢No 0¢
—
N/A
$265
0%
N/A
N/A
N/A
polymarket

Map Handicap: M80 (-1.5) vs Voca (+1.5)

100%
Yes 100¢No 0¢
—
N/A
$119
0%
N/A
N/A
N/A
polymarket

O/U 2.5 Games

0%
Yes 0¢No 100¢
—
N/A
$112
0%
N/A
N/A
N/A
Total markets: 7

Description

This event group covers a Counter-Strike: Global Offensive best-of-three match between M80 and Voca in the ESL Challenger League North America Cup 1 Playoffs, scheduled for February 22, 2026 at 9:00 PM ET. Markets span match winner, individual map winners, total maps played, and map handicap outcomes across Kalshi and Polymarket platforms.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi's match winner market lacks explicit edge-case definitions for forfeits, walkovers, cancellations, and ties, while Polymarket provides detailed resolution rules distinguishing completed matches with forfeits from incomplete matches and cancellations. This creates ambiguity in how Kalshi would resolve under adverse scenarios.Hero tip: Treat Polymarket's resolution framework as the reference standard for edge cases. For Kalshi, assume that a forfeit or walkover by either team before match start would resolve ambiguously; request clarification from Kalshi support. All map-level markets (Map 1 Winner, Map 2 Winner) align on HLTV as primary source with 2-hour credible-reporting fallback. The 7-day delay threshold and 50-50 tie-resolution rule are consistent across Polymarket markets.

Critical divergence points:

  • Kalshi: Match winner market resolves Yes if either M80 or Voca wins. No explicit rules for forfeits, walkovers, cancellations, or ties. Ambiguity: does a pre-match walkover resolve Yes to the winning team, or does it fail to resolve? Key Quote: 'If M80 wins the ESL Challenger League North America Cup 1 2026: M80 vs. Voca CS2 match... then the market resolves to Yes.'
  • Polymarket: Match winner market resolves M80 or Voca if match is completed with a winner. Forfeits/walkovers before start resolve 50-50. Incomplete matches with mid-series forfeit resolve to the winning team. Cancellations, ties, or delays beyond 7 days resolve 50-50. Key Quote: 'If the match ends in a forfeit, disqualification, or walkover (team withdraws before the start and the other wins automatically), this market will resolve to 50-50.'
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.