Will there be a coup attempt in Russia by 2026? [ resolves 2026-12-31 (178D) ]
Russia coup attempt in 2026?
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 | ||
|---|---|---|---|---|---|---|---|---|
| Russia coup attempt in 2026 | 2026-12-31 | 8.0% | $159 | $42K | C | 0xf91ca5…3c7d |
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| polymarket | Whitelisted Proposers | uncommitted | not provided | Optimistic Oracle (UMA) | Other | — |
verbatim rules
polymarket
This market will resolve to "Yes" if there is a widely reported coup attempt in Russia at any point between market creation and December 31, 2026, 11:59 PM ET. Otherwise, this market will resolve to "No."
A coup attempt is defined as a coordinated and deliberate effort by military, security forces, or other state actors (or factions thereof) to overthrow or unlawfully seize control of the Russian government or its leadership. Revolutionary actions by non-state forces, isolated protests, or general unrest will not alone qualify.
Claims by the Russian government that a coup attempt was foiled—such as through arrests or disruption of a planned operation—will only count toward a "Yes" resolution if credible independent sources widely report and explicitly characterize the event as a coup attempt. Foiled plots or arrests that occur without any attempted execution of the coup will not qualify.
The resolution source will be a consensus of credible reporting.
platform source field
polymarket.resolutionSource → ∅ no committed source — see rules text above 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/russia-coup-attempt-in-2026/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/russia-coup-attempt-in-2026 |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("russia-coup-attempt-in-2026") |
| 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-VQ54FPF5J5",
"slug": "russia-coup-attempt-in-2026",
"question": "Will there be a coup attempt in Russia by 2026?",
"category": "geopolitics",
"tags": [
"geopolitics",
"russia",
"political-instability",
"2026",
"coup-d-etat",
"regime-change"
],
"venues_covered": [
"polymarket"
],
"market_count": 1,
"cumulative_volume_usd": 41854,
"resolution_clarity_grade": "C",
"rcg_score": 10,
"rcg_caps": [
"multi_source_no_conflict_rule",
"discretionary_trigger_no_source",
"adversarial_ground_truth",
"commitment_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"
}
}
}