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
Tour
All
Sports
LoL: Galions vs Joblife (BO1) - LFL Regular Season
kalshi
polymarket

LoL: Galions vs Joblife (BO1) - LFL Regular Season

Volume:
$74,870

Match Winner

all

2 markets

Polymarket

Kalshi

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 23, 2026

Closed: Apr 22, 9:00 PM EST

polymarket

Polymarket

View
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
polymarket

Match Winner

View
100%
Yes 100¢No 0¢
—
N/A
$59,506
N/A
N/A
N/A
Settled
Yes
kalshi

Galions

100%
Yes 100¢No 0¢
—
N/A
$10,842
N/A
N/A
$10,333
Settled
Yes
kalshi

Joblife

0%
Yes 0¢No 100¢
—
N/A
$4,443
N/A
N/A
$4,337
Settled
No
polymarket

Any Player Penta Kill

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

Odd/Even Total Kills

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

Both Teams Slay Baron Nashor

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

Both Teams Slay a Dragon

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

Any Player Quadra Kill

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

Both Teams Destroy Inhibitors

0%
Yes 0¢No 100¢
—
N/A
N/A
N/A
N/A
N/A
Settled
No
Total markets: 9

Description

This event group covers a League of Legends Best-of-One match between Galions and Joblife in the LFL Regular Season, scheduled for April 22, 2026 at 2:00 PM EDT. Markets span match outcome, in-game objectives (inhibitors, Baron, dragons), kill statistics (total kills parity, quadra/penta kills), and specific player achievements during Game 1.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi market uses a binary YES resolution for either team winning, while Polymarket markets require specific in-game events or match outcomes with detailed forfeit/cancellation rules. The Kalshi market conflates both possible outcomes into a single YES condition, creating asymmetric resolution logic.Hero tip: On Kalshi, the market resolves YES if either Joblife OR Galions wins—meaning there is no NO outcome unless the match is canceled or delayed beyond 7 days. On Polymarket, each market has distinct YES/NO outcomes tied to specific events (inhibitors, kills, dragons, etc.) or match winner. If betting on Kalshi, you have no downside protection; if betting on Polymarket match winner, you have a true binary with 50-50 resolution for forfeits.

Critical divergence points:

  • Polymarket: Six distinct markets covering match winner (Galions vs Joblife), and five in-game events (inhibitors, kills parity, Baron, dragons, quadra/penta kills). Each market has explicit YES/NO outcomes. Match winner resolves to 50-50 on forfeit, disqualification, or walkover before start. In-game markets resolve to 50-50 if Game 1 is never played, canceled, or delayed beyond 7 days. Key quote: 'If the match ends in a forfeit, disqualification, or walkover (team withdraws before the start and the other wins automatically), this market will resolve to 50-50.'
  • Kalshi: Single binary market: 'If Joblife wins...then resolves YES. If Galions wins...then resolves YES.' This creates a logical structure where both possible match outcomes trigger YES. No explicit NO condition is stated for either team winning. Key quote: 'If Joblife wins the LFL 2026: Joblife vs. Galions...match...then the market resolves to Yes. If Galions wins the LFL 2026: Joblife vs. Galions...match...then the market resolves to Yes.'
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.