RankingsNarrativeEventsWatchlistsAlertsResolvedLearnResearch

Navigate

Prediction markets, watchlists, and tools

RankingsNarrativeEventsWatchlistsAlertsResolvedLearnResearchWatchlistHeatmap

CoinMarketCap for prediction markets.

Track every Polymarket prediction market with live prices, rankings, resolved outcomes, and research.

Trade on Polymarket↗

Markets

  • Rankings
  • Events
  • Topics
  • Ecosystem

Predictions

  • 2028 election odds
  • Bitcoin odds
  • Fed rate odds
  • Trump odds
  • World Cup odds

Resolved

  • Overview
  • Recently resolved
  • High volume
  • Biggest surprises
  • Calibration

Learn

  • Learn hub
  • How markets work
  • How to read odds
  • Is Polymarket accurate?
  • Glossary

Research

  • Research hub
  • Methodology
  • Price discovery
  • Insider trading
  • Brand kit

© 2026 Polyguana. Prediction market intelligence — not investment advice.

Referral disclosure: Polyguana may earn commissions from eligible Polymarket signups and trading activity.

Networkpm.wiki↗canton.wiki↗perp.wiki↗
Resolved answer·LoL: Top Esports vs Invictus Gaming (BO3) - LPL Group Ascend·#1235227

Series: Most towers?

Yes
Final answerResolved Jan 25, 2026

This market settled Yes on Jan 25, 2026.

Outcome: Yes on Jan 25, 2026. Event family: LoL: Top Esports vs Invictus Gaming (BO3) - LPL Group Ascend. $774 traded before settlement. Question: Series: Most towers?

ResolvedJan 25, 2026
Volume$774
Archive coverageSettlement/book only
Open original marketBrowse related resolved
Series: Most towers?
Market imageYes
Last observed Yes—
01Section 01 of 04Movement

Movement

Settlement evidence only

A full price path was not preserved for this market, but the settlement record is firm: it resolved Yes, with $774 traded before close.

Archive movement view

No price turn preserved

Settlement receipt replaces the missing curve

External pre-settlement price history for this market is no longer recoverable. The page now surfaces the trustworthy settlement, book, and source evidence directly instead of leaving an empty price-development module.

Final outcome

Yes

Resolved Jan 25, 2026

Closing spread

0.1¢

Settlement-adjacent bid-ask quality

Source anchor

Original Polymarket market

Use the original market page for rules text when no standalone resolution source was preserved.

0%50%100%No turn point preservedOnly the final settlement evidence is available for this market.

Settled

100%

Final recorded outcome: Yes

02Section 02 of 04Context

Context

Public context

This page has reliable settlement and source-link context, but no preserved pre-settlement price path. It labels that archive gap directly so the final Yes outcome is not mistaken for a reconstructed crowd-opinion curve.

Original Polymarket marketmarket source

Use the original market page for rules text when no standalone resolution source was preserved.

Open market
Crowd state
TrackedRead the final outcome together with the archived movement path and related market family.
Public anchor
Original Polymarket marketUse the original market page for rules text when no standalone resolution source was preserved.
Resolved
Jan 25, 2026Yes settlement with $774 traded before close.
Closing book partialArchive evidence

The archive preserved partial settlement-adjacent book quality: 0.1¢ spread and liquidity not preserved.

03Section 03 of 04Evidence

Evidence

What the archive still preserves

This ledger separates observed prices, settlement facts, and stored notes so you can tell what was actually archived before the market resolved.

Source

Supabase primary

Last refreshed

January 25, 2026 at 6:38 PM UTC

State

Primary · live · primary

Ranking logic

/research/methodology

Resolution source

Polymarket settlement record

Data caveat

Thin books and wide spreads can distort price precision

CheckpointValueSourceDetail
Observed prices
Close certainty100%Observed
04Section 04 of 04Continue

Continue

Continue through the resolved archive

Keep moving through the same family, event, topic, or entity instead of dead-ending after one settlement page.

NBA Playoffs: Who Will Win Series? - Lakers vs. Rockets
Same entity: SeriesYes

NBA Playoffs: Who Will Win Series? - Lakers vs. Rockets

NBA Playoffs: Who Will Win Series? - Lakers vs. Rockets · $1.4M traded · May 2, 2026

Open resolved page
Same entity: Invictus GamingNo

League of Legends: Invictus Gaming vs. Bilibili Gaming

League of Legends: Invictus Gaming vs. Bilibili Gaming · $1.2M traded · Sep 9, 2025

Open resolved page
Spike signal
UnknownNo movement anchor was preserved strongly enough to score a late spike.
Spread
0.1¢Last archived bid-ask spread before settlement.
Liquidity
MissingThe archive did not preserve final liquidity for this market.
Curve
Not recoverableThe page shows a settlement evidence receipt because a full price path is unavailable.
How one-sided the market looked at the close based on the last archived price.
Closing book
Closing spread0.1¢ObservedLast archived bid-ask spread before settlement.
Settlement
Resolution sourcePolymarket settlement recordStored noteNo external oracle URL was stored for this resolved market.
Source contextOriginal Polymarket marketObservedUse the original market page for rules text when no standalone resolution source was preserved.Open market
Same entity: Top EsportsYes

LoL: T1 vs Top Esports (BO5)

LoL: T1 vs Top Esports (BO5) · $12.4M traded · Nov 2, 2025

Open resolved page
Same entity: Top EsportsNo

LoL: G2 Esports vs Top Esports (BO5)

LoL: G2 Esports vs Top Esports (BO5) · $6.1M traded · Oct 30, 2025

Open resolved page
Same entity: Top EsportsYes

LoL: Top Esports vs Team WE (BO5) - LPL Playoffs

LoL: Top Esports vs Team WE (BO5) - LPL Playoffs · $1.1M traded · Jun 7, 2026

Open resolved page
Same entity: Top EsportsYes

LoL: JD Gaming vs Top Esports (BO5) - LPL Playoffs

LoL: JD Gaming vs Top Esports (BO5) - LPL Playoffs · $2.8M traded · Feb 24, 2026

Open resolved page
Same entity: Top EsportsYes

LoL: Weibo Gaming vs Top Esports (BO5) - LPL Playoffs

LoL: Weibo Gaming vs Top Esports (BO5) - LPL Playoffs · $2.7M traded · Mar 2, 2026

Open resolved page
Browse the full resolved archive