Iran successfully targets shipping on July 3?
Probability
2¢
1h
-0.1pp
24h
+0.0pp
24h Vol
$284.81
Liquidity
$12.8K
Canonical status
confidence: highSource status (Polymarket)
Derived status (Orrery)
Reason
Active market, expiry beyond the near-expiry window.
Resolution & Risk
LOW risk- End date
- Jul 3, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 1 factor- 01Liquidity
Thin liquidity
Only $12.8k of visible book — small orders can move the line. Treat the probability as a soft estimate.
What to track next
- Set an alert at the next ±5pp probability move so you find out before the next leg.
- Add to your watchlist — Home will show probability deltas since your last visit.
- Compare against sibling markets in the same event below — divergent pricing across related contracts is the cleanest tell.
Verification actions only — never trade recommendations.
Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.
Resolution & Risk
LOW risk- End date
- Jul 3, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Verification Brief
A guided checklist for what must be proven before this market is treated as reliable context.
The market is live. Track source, liquidity, and wording before escalating it to a resolution-sensitive task.
Create trust-state alertVerification goal
Map resolution-relevant sources to the exact criteria needed to avoid misreading price as settlement.
What needs proof
Primary source
requiredConfirm the primary news consensus source and whether it directly answers the market's resolution question.
Current evidence: consensus of credible reporting
Contract wording
requiredExtract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.
Orrery verification task Iran successfully targets shipping on July 3? State: Live — live monitoring Need sources for: 1. Primary source: Confirm the primary news consensus source and whether it directly answers the market's resolution question. 2. Contract wording: Extract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule. Drop only durable links that map to one criterion. Research only. Not trade advice.
Orrery verification brief Iran successfully targets shipping on July 3? State: live monitoring Verify: Primary source + Contract wording Price is not settlement. Research only. Not trade advice.
Market link goes in reply
A controlled loop for durable sources. Every source must answer one criterion from this Verification Brief.
Sources
0
Criteria covered
0
Reviewed
0
Awaiting review
0
Submit a source mapped to a criterion
Recent source checks
Pilot audit summary
Research only · Not trade advice · Every source maps to one criterion
Timeline
critical · price · trade flowCritical
- Jul 3, 23:59 UTCScheduled resolutionLOW
Market resolves in 169.9h
Price movement
+0.0pp over the last 24h, now 2¢.
Recent Trades
No recent trades visible from the Data API for this market. That usually means liquidity is thin or this market is between event windows.
Related Markets
14- 4¢0.0
Iran successfully targets shipping on July 4?
Geopolitics · Vol $415.45
- 9¢0.0
Iran successfully targets shipping on June 27?
Geopolitics · Vol $10.7K
- 6¢0.0
Iran successfully targets shipping on June 28?
Geopolitics · Vol $2.8K
- 6¢0.0
Iran successfully targets shipping on July 7?
Geopolitics · Vol $2.6K
- 23¢0.0
Iran successfully targets shipping on July 8?
Geopolitics · Vol $9.99
- 4¢0.0
Iran successfully targets shipping on June 26?
Geopolitics · Vol $35.3K
- 7¢0.0
Iran successfully targets shipping on July 5?
Geopolitics · Vol $988.30
- 5¢0.0
Iran successfully targets shipping on July 6?
Geopolitics · Vol $324.24
- 35¢-1.0
Will Cabo Verde win on 2026-06-26?
Geopolitics · Vol $2.7M
- 38¢+2.0
Will Saudi Arabia win on 2026-06-26?
Geopolitics · Vol $2.4M
- 5¢-0.1
Strait of Hormuz traffic returns to normal by end of June?
Geopolitics · Vol $1.7M
- 0¢-0.1
Kharg Island no longer under Iranian control by June 30?
Geopolitics · Vol $768.9K
- 12¢+2.0
Putin out as President of Russia by December 31, 2026?
Geopolitics · Vol $758.7K
- 0¢-0.2
Will JD Vance enter Iran by June 30?
Geopolitics · Vol $733.1K
Market Description
This market will resolve to "Yes" if Iranian forces conduct a kinetic strike on or seize control of a commercial ship on the specified date IRST (UTC +3:30). Otherwise, this market will resolve to "No". Attacks on military vessels will not be considered. Only military actions by Iranian forces explicitly claimed by the Islamic Republic of Iran or confirmed to have originated from Iranian territory or been carried out by Iranian forces will count toward the resolution of this market. Attacks by proxy forces (i.e. Hezbollah, Houthis, etc.) will not count toward the resolution of this market. Missile/drone strikes targeting a ship that are intercepted or otherwise do not directly impact the vessel will not be considered, regardless of damage through debris. Seize control refers to Iranian forces forcefully boarding and taking control of a commercial ship. Qualifying incidents include, but are not limited to, drone and missile strikes, aerial bombings, and kinetic actions carried out by Iranian operatives in person, such as seizing a ship by force. The primary resolution source for this market will be a consensus of credible reporting. If a kinetic incident occurs, but, on the specified date, 11:59 PM IRST, material ambiguity remains as to the exact timing of the incident, or whether the incident can be attributed to Iran, this market may remain open for an additional 3 calendar days, IRST. If, at such time, the attribution or timing of the incident still cannot be confirmed, this market will resolve to “No”.
Why this category?
confidence: highCategory
Source
Matched term
iranReason
Question text contains the high-signal keyword "iran" — matched the Geopolitics rule.
Categories come from a deterministic engine: manual overrides (highest priority) → sports hard markers → event-tag rules → keyword rules → Gamma category hint → default. The engine is versioned in category-overrides.ts; methodology lives at /methodology.
FAQ — questions readers actually ask
What is the current Polymarket probability for "Iran successfully targets shipping on July 3?"?
As of Fri, 26 Jun 2026 22:04:42 GMT, YES is priced at 2% implied probability on Polymarket. The price changed +0.0pp in the last 24 hours, -0.1pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Jul 3, 2026 (2026-07-03T23:59:00.000Z). Resolution is determined from the market description on Polymarket.
What source determines the outcome?
Resolution is sourced from the market description on Polymarket. Polymarket's UMA optimistic oracle is the final settlement layer; if the published source is ambiguous, UMA tokenholders adjudicate. Source-extraction confidence is shown in the Resolution & Risk block above.
How much is being traded on this market?
$284.81 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $284.81. Open liquidity in the YES/NO orderbooks: $12.8K. Spread between best bid and best ask: 2.9¢.
Is this a trade recommendation?
No. Orrery describes — never predicts. Every signal on this market carries explicit Evidence, Backtest, and Action tiers. The Action is always one of: Watch only, Inspect timeline, Create alert, Verify source, or Ignore — never Buy or Sell. The probability above is the market's collective implied probability, not a forecast Orrery is publishing.
How fresh is this data and where does it come from?
This page revalidates from the public Polymarket APIs every 30 seconds. Probability and 24h-change come from Gamma; the chart series comes from the CLOB orderbook history; trade and holder data come from the Data API. The fetched-at timestamp on each block tells you exactly how old the underlying upstream pull was.
Alerts
In-app banners fire as soon as a rule is satisfied. Email digests are wired to a server-side cron and continue while your tabs are closed. Telegram and Discord are planned — every existing rule will keep working as channels light up.