How did this market resolve?

It resolved Yes on Jul 11, 2026 on Polymarket. Event family: Wimbledon Juniors, Boys (Doubles): Miguel/Sesko vs Antonius/Johnson.

What source was used to resolve it?

No external resolution source URL was stored for this market in the archived metadata. Original Polymarket market is attached as public context for interpreting the result.

Yes — Wimbledon Juniors, Boys (Doubles): Miguel/Sesko vs Antonius/Johnson (Jul 11, 2026)

Wimbledon Juniors, Boys (Doubles): Miguel/Sesko vs Antonius/Johnson

Yes

Final answerResolved Jul 11, 2026

A close one — the market was only 50% confident in Yes at the close.

“Wimbledon Juniors, Boys (Doubles): Miguel/Sesko vs Antonius/Johnson” resolved Yes on Jul 11, 2026, after $36 traded on Polymarket.

ResolvedJul 11, 2026

Volume$36

Archive coverageCurve + partial book

Movement

How opinion moved into resolution

The market sat near 37% before it climbed to 100% into settlement — a 63-point move.

Yes 50.0¢ALL+29.9%

Yes50.0¢No50.0¢

Last observed Yes

50% (50¢)

Settled result

Yes

This question is still liveThe archive shows how it settled — these markets are trading now.

Wimbledon Juniors, Boys: Completed Match: Miguel/Sesko vs Antonius/JohnsonSame event90%+40.0%$0Trade on Polyguana →Miguel/Sesko vs. Antonius/Johnson: Total Sets O/U 2.5Same event90%-40.0%$0Trade on Polyguana →Set 2 Winner: Miguel/Sesko vs Antonius/JohnsonSame event90%+40.0%$0Trade on Polyguana →

Context

Schedule and result context

The resolved archive connects final outcome, price path, preserved book quality, and source context so the market can be read as a public forecast record rather than just a final Yes/No label.

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

Jul 11, 2026Yes settlement with $36 traded before close.

Closing book partialOrder book

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

Spike signal

No spikeThe preserved anchor-to-close move is small; this resolved as a stable or consensus market.

Spread

1¢Last archived bid-ask spread before settlement.

Liquidity

MissingThe archive did not preserve final liquidity for this market.

Curve

4 pointsEnough preserved points to render price development.

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

July 11, 2026 at 12:00 PM UTC

State

Primary · fresh · fresh cache

Ranking logic

/research/methodology

Resolution source

UMA oracle

Data caveat

Thin books and wide spreads can distort price precision

Observed prices

First archived price38.5% (38.5¢)ObservedEarliest preserved observation in the resolved-market archive.

24h before settle38.5% (38.5¢)ObservedCheckpoint preserved around one day before the official settlement time.

Last observed price50% (50¢)ObservedClosest archived market price before settlement.

Close certainty50%ObservedHow one-sided the market looked at the close based on the last archived price.

Surprise score12 ptsObservedAbsolute move from the stored anchor into the final observed pre-settlement price.

Closing book

Closing spread1¢ObservedLast archived bid-ask spread before settlement.

Settlement

Resolution sourceUMA oracleObservedThis market carried UMA-linked metadata, but the archive did not retain a market-specific oracle URL.Open source

Source contextOriginal Polymarket marketObservedUse the original market page for rules text when no standalone resolution source was preserved.Open market

Continue through the resolved archive

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

Browse the full resolved archive