This event group covers a Counter-Strike 2 best-of-three match between ex-RUBY and Lavked in the CCT Europe Series #19 Playoffs, scheduled for April 1, 2026 at 4:00 AM EDT. Markets span match winner, individual map winners, and granular statistics (rounds and kills per map), with resolution sourced from HLTV.org.
Kalshi provides minimal resolution criteria (binary Yes/No on match outcome only), while Polymarket offers comprehensive edge-case handling for forfeits, walkovers, cancellations, delays, and incomplete matches. This creates divergent outcomes in non-standard scenarios.
Hero Tip:
Prioritize Polymarket's detailed rules as the authoritative framework. If the match faces cancellation, delay beyond 7 days, or forfeit/walkover before play, expect Polymarket to resolve 50-50. Kalshi's ambiguity in these scenarios makes it higher-risk. Verify match status on HLTV.org within 2 hours of scheduled conclusion.
Critical Divergence Points:
Kalshi:
Binary Yes/No resolution: 'If Lavked wins... then Yes' and 'If ex-RUBY wins... then Yes'. No explicit rules for forfeits, walkovers, cancellations, delays, or incomplete matches. Ambiguous whether a forfeit/walkover counts as a 'win' for resolution purposes.
Polymarket:
Comprehensive edge-case rules: Forfeits/walkovers/disqualifications before play begins resolve 50-50; incomplete matches with one team winning by opponent forfeiture resolve 50-50; cancellations or delays beyond 7 days without a winner resolve 50-50. 'If the match ends due to the clinching map being forfeited this will count as a completed match.' Explicit 2-hour HLTV.org publication window before consensus reporting is used.
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.