TOTAL VOLUME:

$134.1b

24H VOL:

$133,388,117

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,436,095,462

405,232

Markets across

30,526

events

MATCHED EVENTS:

2,693

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
Valorant: sleepers vs M80 (BO3) - VCL North America Playoffs
polymarket
kalshi

Valorant: sleepers vs M80 (BO3) - VCL North America Playoffs

Volume:
$83,332

Match Winner

 - Polymarket

Match Winner - Polymarket

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Feb 24, 2026

Valorant: sleepers vs M80 (BO3) - VCL North America Playoffs

100%chance
Amount

$

Trade on
polymarket

Trade on Polymarket

At 100¢ buys you 100 shares | Odds: 100% Total Payout: $100 | Net Profit: $0 Multiplier: 1.00x | ROI: 0% | APY: N/A Illiquid market
You will be redirected to the platform to complete this trade.
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
polymarket

Match Winner

100%
Yes 100¢No 0¢
—
N/A
$26,944
0%
N/A
N/A
N/A
kalshi

sleepers

100%
Yes 100¢No 0¢
—
N/A
$21,098
0%
0%
$11,802
N/A
polymarket

Map 2 Winner

100%
Yes 100¢No 0¢
—
N/A
$6,333
0%
N/A
N/A
N/A
polymarket

Map 1 Winner

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

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

100%
Yes 100¢No 0¢
—
N/A
$185
0%
N/A
N/A
N/A
kalshi

M80

0%
Yes 0¢No 100¢
—
N/A
$28,122
0%
0%
$16,329
N/A
polymarket

O/U 2.5 Games

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

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

0%
Yes 0¢No 100¢
—
N/A
$97
0%
N/A
N/A
N/A
Total markets: 8

Description

This event group covers a best-of-three Valorant match between sleepers and M80 in the VCL North America Playoffs scheduled for February 23, 2026. Markets span match winner, map totals, map handicaps, and individual map outcomes across Polymarket and Kalshi platforms.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Polymarket provides detailed, multi-market resolution logic with explicit forfeit and walkover handling, while Kalshi offers a single binary market with no edge-case definitions. Additionally, scheduled times conflict (4:00 PM ET vs 6:15 PM ET).Hero tip: Use Polymarket markets for precise exposure to match outcomes and map-level dynamics. Treat Kalshi as a simple binary bet with elevated settlement ambiguity. Verify official match time with VCL before execution. If a forfeit or walkover occurs, expect Polymarket markets to resolve to 50-50 while Kalshi's resolution remains undefined.

Critical divergence points:

  • Polymarket: Five distinct markets (match winner, games total O/U 2.5, map handicap M80 -1.5, map handicap SLP -1.5, map 1 winner, map 2 winner) with unified resolution logic. All reference vlr.gg as primary source with 2-hour credible reporting fallback. Scheduled 4:00 PM ET. Forfeits/walkovers mid-match resolve to 50-50; completed forfeits on clinching map count as completed match. Key quote: 'If the match begins but is not completed, and one team wins due to the opponent's match forfeiture, disqualification, or walkover, this market will resolve to 50-50.'
  • Kalshi: Single binary market with minimal resolution logic: 'If M80 wins... Yes. If sleepers wins... Yes.' No handling of cancellations, forfeits, walkovers, or incomplete matches. One description references 6:15 PM ET (conflicting with Polymarket's 4:00 PM ET). No resolution source specified. Ambiguity on whether a forfeit/walkover resolves to Yes or remains unresolved.
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.