This event group covers a best-of-three League of Legends match between Ninjas in Pyjamas and Anyone's Legend in the LPL Group Ascend, originally scheduled for April 22, 2026 at 7:00 AM ET. The markets span series-level outcomes (match winner, game count, handicap), individual game winners (Games 1–3), and in-game objective metrics (Baron/Dragon slays, inhibitor destruction, kill counts, and multi-kill achievements). All markets reference gol.gg as the primary resolution source, with credible reporting consensus as a secondary fallback if results are not published within 2 hours of event conclusion.
Unified Resolution Criteria (Consistent across platforms)
Both Polymarket and Kalshi resolve based on the outcome of the LoL match between Ninjas in Pyjamas and Anyone's Legend in the LPL Group Ascend scheduled for April 22, 2026 at 7:00 AM EDT, with consistent treatment of cancellations, delays beyond 7 days, forfeits, and official resolution via gol.gg or credible reporting.
Primary resolution logic:
Official information from https://gol.gg/esports/home; if unavailable within 2 hours of event conclusion, consensus of credible reporting including video evidence.
Core resolution logic:
The match series resolves based on which team wins the best-of-3 match: Ninjas in Pyjamas or Anyone's Legend.
Individual game markets (Game 1, Game 2, Game 3 winners) resolve based on the winner of that specific game if played.
Objective-based markets (Baron, Dragon, Inhibitor, Kill counts, Penta/Quadra kills) resolve based on whether the specified condition occurred during the designated game.
Series-level markets (O/U 2.5 games, Game Handicap) resolve based on total games played and the margin of victory.
If the match is canceled entirely, delayed beyond 7 days without play beginning, or ends in a tie, all markets resolve 50-50.
If a game is not played due to series clinch, forfeit, disqualification, or walkover, game-specific markets resolve 50-50.
If a game begins but is not completed, objective and kill markets resolve based on conditions met prior to stoppage; if conditions are not met, they resolve No.
Games won by forfeit, disqualification, walkover, or default count toward series totals and handicap calculations, provided the match is completed.
If the match begins but is not completed and one team wins due to opponent forfeiture/disqualification/walkover, series-level markets resolve 50-50; however, if the clinching game itself is forfeited, the match counts as completed.
Kalshi's binary market (Anyone's Legend wins OR Ninjas in Pyjamas wins) resolves Yes if either team wins the match, ensuring exactly one outcome resolves Yes.
Edge cases & Clarifications:
Series Clinch Before Game 3: If a team clinches the series 2-0 before Game 3 is played, all Game 3-specific markets (winner, objectives, kills) resolve 50-50. Series-level markets (O/U 2.5, Handicap) resolve based on the 2-0 result.
Game Remade Mid-Series: If any game is remade, resolution for that game is based solely on the remade game. Prior iterations do not count.
Incomplete Game with Surrender: If a game ends via surrender before completion, objective markets (Baron, Dragon, Inhibitor) resolve based on whether both teams met the condition prior to surrender. If the condition was not met, the market resolves No.
Execution vs Champion Kill: For kill-count markets (Odd/Even Total Kills), only champion-to-champion kills count. Executions to turrets, minions, or neutral monsters do not count toward the total.
Elder Dragon vs Elemental Dragon: For dragon markets, only elemental dragons (Infernal, Mountain, Ocean, Hextech, Chemtech, Cloud) count. Elder Dragon kills do not count toward the Both Teams Slay a Dragon condition.
Timing:
Resolution occurs upon official publication by gol.gg within 2 hours of event conclusion, or upon consensus of credible reporting if gol.gg is unavailable. For series-level markets, resolution occurs when the match outcome is determined. For game-specific markets, resolution occurs when that game concludes or the series is clinched.
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.