TOTAL VOLUME:

$134.1b

24H VOL:

$141,541,542

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,440,096,988

406,065

Markets across

30,522

events

MATCHED EVENTS:

2,692

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
Call of Duty: FaZe Vegas vs Boston Breach (BO5) - Call of Duty League Stage 2 Major Qualifiers Qualifiers
kalshi
polymarket

Call of Duty: FaZe Vegas vs Boston Breach (BO5) - Call of Duty League Stage 2 Major Qualifiers Qualifiers

Volume:
$62,133

Boston Breach

 - Kalshi

Boston Breach - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 2, 2026

Closed: Mar 1, 8:30 PM 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

Boston Breach

View
100%
Yes 100¢No 0¢
—
N/A
$22,929
N/A
N/A
$19,328
Settled
Yes
polymarket

Game 1 Winner

View
100%
Yes 100¢No 0¢
—
N/A
$1,270
N/A
N/A
N/A
Settled
Yes
polymarket

O/U 3.5 Games

View
100%
Yes 100¢No 0¢
—
N/A
$202
N/A
N/A
N/A
Settled
Yes
kalshi

FaZe Vegas

View
0%
Yes 0¢No 100¢
—
N/A
$18,212
N/A
N/A
$13,851
Settled
No
polymarket

Match Winner

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

Game 2 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$4,779
N/A
N/A
N/A
Settled
No
polymarket

Game Handicap: FAZE.V (-2.5) vs Boston Breach (+2.5)

View
0%
Yes 0¢No 100¢
—
N/A
$389
N/A
N/A
N/A
Settled
No
polymarket

Game 4 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$183
N/A
N/A
N/A
Settled
No
polymarket

Game 3 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$107
N/A
N/A
N/A
Settled
No
polymarket

O/U 4.5 Games

View
0%
Yes 0¢No 100¢
—
N/A
$104
N/A
N/A
N/A
Settled
No
polymarket

Game Handicap: FAZE.V (-1.5) vs Boston Breach (+1.5)

View
0%
Yes 0¢No 100¢
—
N/A
$103
N/A
N/A
N/A
Settled
No
Total markets: 11

Description

This event group covers a best-of-five Call of Duty League match between FaZe Vegas and Boston Breach scheduled for March 1, 2026 at 4:30 PM ET as part of the Stage 2 Major Qualifiers. The group includes markets on match winner, individual game winners (Games 1-4), total games played, and game handicaps.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi's match winner market contains a logical contradiction where both FaZe Vegas winning and Boston Breach winning resolve to Yes, making the market fundamentally unresolvable. Polymarket's equivalent market is properly structured with binary outcomes.Hero tip: Do not trade the Kalshi match winner market due to the logical impossibility. Use Polymarket for match winner exposure. All other markets (game winners, totals, handicaps) across both platforms share consistent resolution logic and can be traded with confidence.

Critical divergence points:

  • Kalshi: Match winner market has critical flaw: both Boston Breach winning and FaZe Vegas winning are stated to resolve to Yes. Quote: 'If Boston Breach wins...then the market resolves to Yes. If FaZe Vegas wins...then the market resolves to Yes.' This creates a non-binary, unresolvable market.
  • Polymarket: Match winner market is properly structured: resolves to FaZe Vegas if they win, Boston Breach if they win, or 50-50 for cancellation/tie/delay beyond 7 days/forfeit/disqualification/walkover. Quote: 'This market will resolve to FaZe Vegas if FaZe Vegas win the match...This market will resolve to Boston Breach if Boston Breach win the match...If the match is canceled...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.