Market detail
Series: LNG Esports Kill Handicap (-14.5)
Escalated → DVMResolved
Risk factor breakdown
transparent weighted sum → 0/100Dispute & reset timeline
7 on-chain eventsunverified — derived from on-chain event timestamps; lifecycle ordering not independently audited.
- ●InitializedJan 15, 2026, 14:40
- ✕Disputed (round 1)Jan 28, 2026, 02:26
- ↺Reset (round 1)Jan 28, 2026, 02:26
- ↗Escalated to mainnet DVM (round 1)Jan 28, 2026, 02:26escalated to mainnet DVM ↗
- ◆Proposed (round 1)Feb 3, 2026, 18:56
- ✓Settled (round 1)Feb 3, 2026, 21:07
- ✓ResolvedFeb 3, 2026, 21:12
Resolution status
State
Resolved
Reset rounds
0
Pause count
0
Resolution lag
19d 6h
On-chain provenance
auditablequestionId
Polymarket slug/lol-lng-up-2026-01-16-kill-handicap-away-14pt5
Adapter address
Risk score0/100 · Low
Off-chain clarifications0
✓
No disputes recorded
This market has no on-chain dispute, reset, or DVM escalation on record.
Resolution criteria
ancillaryText · rendered from on-chain ancillaryDataq: title: Series: LNG Esports Kill Handicap (-14.5), description: This market refers to the LoL match between LNG Esports and Ultra Prime in the LPL Group Nirvana, scheduled for January 16 at 4:00AM ET.
This market will resolve to "LNG Esports" if LNG Esports secures 15 or more kills than Ultra Prime in the match.
Otherwise, it will resolve to "Ultra Prime".
If the match is canceled (not played at all), ends in a tie, or is delayed beyond 7 days from the scheduled date without a winner determined, this market will resolve to 50-50.
If the match begins but is not completed, and one team wins due to the opponent's forfeiture, disqualification, or walkover, this market will resolve to 50-50.
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. market_id: 1190351 res_data: p1: 0, p2: 1, p3: 0.5. Where p1 corresponds to Ultra Prime, p2 to LNG Esports, p3 to unknown/50-50. Updates made by the question creator via the bulletin board at 0x65070BE91477460D8A7AeEb94ef92fe056C2f2A7 as described by https://polygonscan.com/tx/0xa14f01b115c4913624fc3f508f960f4dea252758e73c28f5f07f8e19d7bca066 should be considered.,initializer:91430cad2d3975766499717fa0d66a78d814e5c5