Will Trump visit North Korea by June 30, 2025? [ resolved 2026-06-30 ]
Will Trump visit North Korea by June 30?
polymarket: [C] multiple sources, no tie-break·reporting consensus methodology ›
markets · by resolution date · marks: daily snapshot
polymarket 1 market
| market | resolves | P(YES) | vol (24h) | vol (cum) | RCG | venue id | ||
|---|---|---|---|---|---|---|---|---|
| Will Trump visit North Korea by June 30 | 2026-06-30 | 0.0% | $172 | $24K | C | 0x0ec47e…cb4f |
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| polymarket | Whitelisted Proposers | uncommitted | not provided | Optimistic Oracle (UMA) | Other | — |
verbatim rules
polymarket
If Donald J. Trump visits North Korea by June 30, 2026, 11:59 PM ET, this market will resolve to "Yes". Otherwise, this market will resolve to "No".
For the purpose of this market, a "visit" is defined as Trump physically entering the terrestrial or maritime territory of North Korea. Whether or not Trump enters North Korean airspace during the timeframe of this market will have no bearing on this market's resolution.
The primary resolution source for this information will be official information from Trump, information released by his verified social media accounts, and official information from North Korea; however, a consensus of credible reporting will also be used.
platform source field
polymarket.resolutionSource → ∅ no committed source — see rules text above resolution history
| outcome | market | venue | resolved | final price |
|---|---|---|---|---|
| NO | Will Trump visit North Korea by June 30? | polymarket | 2026-06-30 | 0% |
Derived from the platform price + resolution-date snapshot (1 resolved market). PENDING upgrades to a final outcome on the next refresh.
recent wire items
monitoring status: active no active wire
No CM Signal wire has been published for this event yet.
CM Signal’s news-cycle scan surfaces the day’s top stories alongside the prediction markets pricing them. When a story references this event, its wire is published here and links back to this page.
programmatic access · four surfaces, same payload
One canonical record at every surface — embedded JSON-LD, REST, MCP, and /llms.txt.
| HTML | browsers, AI grounded search, crawlers (embedded JSON-LD @type: Dataset) | https://clearmarket.fyi/events/will-trump-visit-north-korea-by-june-30/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/will-trump-visit-north-korea-by-june-30 |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("will-trump-visit-north-korea-by-june-30") |
| AGENT | AI crawler discovery index | /llms.txt |
Snapshot 2026-07-06. Venue data via Kalshi + Polymarket APIs. Editorial fields (tags, editorial_notes) are ClearMarket-drafted with AI assistance under editorial review. Derived fields (venues_covered, resolution_clarity_grade, rcg_score) computed at serve time. Full per-field map in the JSON record under field_provenance.
raw JSON record · same payload returned by REST endpoint {
"event_id": "CM-EVT-4GRY31QS88",
"slug": "will-trump-visit-north-korea-by-june-30",
"question": "Will Trump visit North Korea by June 30, 2025?",
"category": "geopolitics",
"tags": [
"geopolitics",
"trump",
"diplomacy",
"north-korea",
"2026",
"us-foreign-policy"
],
"venues_covered": [
"polymarket"
],
"market_count": 1,
"cumulative_volume_usd": 24359,
"resolution_clarity_grade": "C",
"rcg_score": 30,
"rcg_caps": [
"multi_source_no_conflict_rule",
"adversarial_ground_truth",
"uncommitted_placeholder"
],
"resolution_source": null,
"resolution_source_url": null,
"source_status": "no_committed_source",
"source_of_record": null,
"resolution_source_list": null,
"arbitration_model": "uma_oracle",
"proposer_model": "managed_whitelist",
"field_provenance": {
"question": {
"source": "clearmarket_editorial"
},
"tags": {
"source": "clearmarket_editorial",
"ai_drafted": true
},
"resolution_clarity_grade": {
"source": "derived",
"method": "rcg_v2_7factor"
},
"venues_covered": {
"source": "derived"
}
}
}