Market detail
Will the highest temperature in Hong Kong be 24°C on May 15?
DisputedEscalated → DVMResolved
Risk factor breakdown
transparent weighted sum → 47/100Dispute & reset timeline
7 on-chain eventsunverified — derived from on-chain event timestamps; lifecycle ordering not independently audited.
- ●InitializedMay 13, 2026, 04:11
- ✕Disputed (round 1)May 14, 2026, 17:01
- ↺Reset (round 1)May 14, 2026, 17:01
- ↗Escalated to mainnet DVM (round 1)May 14, 2026, 17:01escalated to mainnet DVM ↗
- ◆Proposed (round 1)May 18, 2026, 02:31
- ✓Settled (round 1)May 18, 2026, 04:04
- ✓ResolvedMay 18, 2026, 05:51
Resolution status
State
Resolved
Reset rounds
1
Pause count
0
Resolution lag
5d 1h
On-chain provenance
auditablequestionId
Polymarket slug/highest-temperature-in-hong-kong-on-may-15-2026-24c
Adapter address
Risk score47/100 · Elevated
Off-chain clarifications0
Resolution criteria
ancillaryText · rendered from on-chain ancillaryDataq: title: Will the highest temperature in Hong Kong be 24°C on May 15?, description: This market will resolve to the temperature range that contains the highest temperature recorded by the Hong Kong Observatory in degrees Celsius on 15 May '26.
The resolution source for this market will be information from the Hong Kong Observatory, specifically the "Absolute Daily Max (deg. C)" the specified date once information is finalized in the relevant "Daily Extract", available here: https://www.weather.gov.hk/en/cis/climat.htm
This market can not resolve to "Yes" until data for this date has been finalized.
The resolution source for this market measures temperatures in Celsius to one decimal place (eg, 9.1°C). Thus, this is the level of precision that will be used when resolving the market.
Any revisions to temperatures recorded after data is finalized for this market's timeframe will not be considered for this market's resolution. market_id: 2247290 res_data: p1: 0, p2: 1, p3: 0.5. Where p1 corresponds to No, p2 to Yes, p3 to unknown. This request MUST only resolve to p1 or p2. Updates made by the question creator via the bulletin board at 0x69c47De9D4D3Dad79590d61b9e05918E03775f24 should be considered.,initializer:91430cad2d3975766499717fa0d66a78d814e5c5