This event group covers a Best-of-3 Valorant match between Shopify Rebellion Black and FlyQuest in VCL North America Stage 2 Group Stage, scheduled for April 14, 2026 at 7:00 PM EDT. Markets span match winner, map-level outcomes, games total, and map handicaps across Kalshi and Polymarket platforms.
Kalshi match winner market contains a logical contradiction where both possible outcomes (FlyQuest win and Shopify Rebellion win) resolve to Yes, rendering the market unresolvable. Additionally, Polymarket's Map Handicap market (Question 12) lists a different scheduled time (7:10 PM ET) than all other markets (7:00 PM ET).
Hero Tip:
The Kalshi match winner market is fundamentally broken due to logical contradiction and should be avoided or flagged for cancellation. For Polymarket markets, use 7:00 PM ET as the canonical scheduled time and disregard the 7:10 PM timestamp in Question 12 as a data entry error. Focus trading activity on Polymarket's coherent map-level and handicap markets.
Critical Divergence Points:
Kalshi:
Match winner market states: 'If FlyQuest wins... resolves to Yes. If Shopify Rebellion wins... resolves to Yes.' This is a logical contradiction—both mutually exclusive outcomes cannot both resolve to Yes. The market lacks a No outcome definition and is unresolvable as written.
Polymarket:
All markets consistently reference 7:00 PM ET scheduled time except Question 12 (Map Handicap: FQ -1.5 vs SRB +1.5), which states 7:10 PM ET. This is a minor timing discrepancy within Polymarket itself, likely a data entry error. All Polymarket markets otherwise contain coherent, mutually exclusive resolution outcomes.
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.