Market Analysis · Layout v2

US strikes Iran by June 30, 2026? Current market probability and scenario analysis

Data-first analysis of US strikes Iran by June 30, 2026: implied probability, liquidity profile, scenario triggers, execution risk, and fail-closed evidence status.

Published February 25, 2026politics

Open referenced market →

Executive Summary

As of February 25, 2026 (12:07:38 UTC snapshot), the market **US strikes Iran by June 30, 2026?** is pricing YES at 69.5% and NO at 30.5% on the featured card. This is a live snapshot rather than a static forecast. Price is best interpreted as an implied probability under current liquidity and execution conditions. At publication time, displayed 24h volume is about $24.1M and displayed liquidity is about $155K, which means participation is high but execution quality can still vary by depth and spread at the moment of entry. External fact claims are handled in fail-closed mode in this article. See Evidence & Sources for verified references.

Current Market Snapshot

Current probability

YES 69.5% / NO 30.5% (snapshot from market card/API)

24h volume

$24.1M

Liquidity

$155K

Spread

not shown on compact card; confirm in live orderbook before execution

Last update

12:07:38 UTC (from market snapshot)

Resolution date

2026-06-30 (card shows ~4mo remaining)

How the market prices this event

In a binary market, price maps to market-implied probability on a 0 to 1 scale. A YES level near 0.695 means participants are currently assigning higher weight to strike occurrence before June 30, 2026 than to non-occurrence over the same window.

That probability is an equilibrium between buyers and sellers under available depth. If one side aggressively crosses the spread while depth is shallow, short-term price action can overshoot and then mean-revert once resting liquidity refills.

Information flow drives repricing speed. Contracts linked to geopolitical headlines can move quickly on fresh developments, but the persistence of that move usually depends on whether follow-through flow remains and whether liquidity providers continue quoting both sides.

A practical read of this market separates signal into three layers: card-level probability, executable orderbook conditions, and verified external context quality. Treating all three as one signal can create false precision.

Historical context

At publication time, this analysis avoids unsourced external event assertions and focuses on market mechanics. That is important in contracts tied to potential military actions, where headline velocity and verification quality can diverge.

A recurring pattern in medium-horizon geopolitical binaries is phased repricing. First, a fast move follows new information. Second, liquidity conditions determine how much of that move holds. Third, timing to deadline affects whether probability decays, stabilizes, or extends.

Another recurring pattern is sensitivity to interpretation and timing windows. Even when participants broadly agree on directional risk, they can disagree on whether the event is likely to occur within the specific contract horizon, producing frequent rebalancing between YES and NO.

Market Signal vs External Evidence

Market signal (Type A)

The featured snapshot prints YES 69.5% and NO 30.5%.
Displayed 24h volume is about $24.1M and displayed liquidity is about $155K.
The contract is active with a remaining window to June 30, 2026.

External evidence (Type B)

At publication time, we could not verify the minimum set of event-specific external sources required to make factual claims about strike occurrence dynamics.
This article therefore avoids unsourced external factual assertions and stays in market-structure mode.

Unknowns (Type D)

Public evidence links were not found for this specific claim at publication time.

Base rate and comparable cases

A reliable reference-class base rate was not found from reputable sources at publication time.

For this market, contract-horizon sensitivity is a primary driver: probability can remain elevated while uncertainty is broad, then compress or expand as the deadline window narrows and evidence quality changes.

Steelman: YES case vs NO case

YES case (best argument)

If credible new information raises perceived near-term strike likelihood, YES may reprice higher.
If order flow remains persistently one-sided toward YES while depth on NO is absorbed, equilibrium can shift upward.
If timeline-sensitive developments occur well before the resolution date, traders may reduce timing discount.
If market participants interpret the event path as binary and immediate, YES demand can stay structurally firm.

NO case (best argument)

If no qualifying escalation appears as time passes, timing decay can pressure YES lower.
If repeated spikes are not supported by sustained depth and follow-through buying, reversions can favor NO.
If uncertainty remains high but actionable signals stay sparse, participants may reduce premium for immediacy.
If resolution-window discipline tightens in pricing models, NO can gain relative value.

Signal strength

Signal: YES 69.5% / NO 30.5% snapshot; Direction YES; Strength Medium; Reason clear skew but still event-sensitive and reversible; Source? No (market-derived).
Signal: 24h volume about $24.1M; Direction Mixed; Strength Medium; Reason heavy activity can reflect both conviction and hedging; Source? No (market-derived).
Signal: Liquidity about $155K; Direction Mixed; Strength Medium; Reason reasonable depth, but slippage risk remains during bursts; Source? No (market-derived).
Signal: Resolution horizon to 2026-06-30; Direction Mixed; Strength Medium; Reason enough time for repricing in both directions; Source? No (market-derived).
Signal: Missing event-specific verified external links under fail-closed criteria; Direction Mixed-to-NO; Strength Weak-to-Medium; Reason evidence gaps cap confidence in narrative interpretation; Source? Yes (verification process).

What would change our view

Upward triggers (YES)

If a clearly attributable, verifiable development increases perceived strike probability within this contract window.
If evidence that YES-side repricing is supported by sustained depth and tight executable spread appears.
If signals that market participants keep paying up for YES across multiple sessions persist.
If timing-related uncertainty declines while directional risk remains elevated.

Downward triggers (NO)

If no qualifying escalation appears while the remaining window continues to contract.
If evidence that headline-driven YES spikes repeatedly fade after liquidity normalizes accumulates.
If signals that NO-side resting depth consistently absorbs aggressive flow emerge.
If pricing shifts from directional urgency toward time-decay discipline.

Scenario analysis

What could increase probability

If evidence that escalation risk is repriced upward in a sustained, not one-tick, manner.
If signals that orderbook support for YES improves across several price levels appear.
If participants reduce timing discount and treat the deadline window as near enough for action risk.
If volatility expands with directional persistence rather than immediate mean reversion.

What could decrease probability

If no qualifying catalysts appear and time-to-resolution shortens without confirmation.
If evidence that recent upside moves were flow-driven rather than information-driven accumulates.
If signals that NO-side liquidity remains deeper and more stable than YES-side demand appear.
If volatility compresses and repricing becomes range-bound around lower YES levels.

Execution Notes

Before entering, check top-of-book bid/ask, spread (absolute and percent), and depth near your intended size.
If spread is wide / depth is thin, treat pricing as noisy and avoid urgency.
If volatility is event-driven, avoid entries immediately after headline spikes.
Prefer staged execution for size to reduce adverse selection when conditions are fast.
Use limit discipline when possible; marketable pricing can improve immediacy but may increase slippage.
Re-check card timestamp and live orderbook before each execution decision.
Treat resting orders as exposure that may fill under changed information.
Maintain scenario-based discipline rather than reacting to single candles.

Uncertainty and resolution risk

Resolution rule clarity: Medium (event wording is clear, but interpretation timing still matters).
Measurement/definition risk: Medium (headline interpretation may differ from executable confirmation).
Timing risk: Medium-to-High (multi-month window can still compress quickly near key updates).
Information asymmetry risk: Medium (participants with faster monitoring can react earlier).

When probability is extreme, avoid overconfidence. High or low prints can still include liquidity distortions, timing uncertainty, and non-causality between narrative momentum and eventual resolution.

Evidence & Sources

Fail-closed statement:

Public evidence links were not found for this specific claim at publication time.

Claim -> link proofs:

Claim: The live probability, 24h volume, liquidity, and update timestamp used in this article come from the featured snapshot entry for market 984442 -> [PolymarketTrade Featured API snapshot](https://www.polymarkettrade.app/api/markets?category=featured)
Claim: A direct market endpoint for 984442 is available and was used to cross-check timestamp and pricing fields -> [PolymarketTrade market API endpoint](https://www.polymarkettrade.app/api/markets/984442)
Claim: The article anchor mapping to the exact market card is validated through the canonical view+anchor URL format -> [PolymarketTrade market URL (featured anchor)](https://www.polymarkettrade.app/?view=featured#market-featured-984442)

Sources:

[PolymarketTrade] Featured markets API snapshot (market_id 984442) - 2026-02-25. [Open source](https://www.polymarkettrade.app/api/markets?category=featured)
[PolymarketTrade] Market API snapshot for 984442 - 2026-02-25. [Open source](https://www.polymarkettrade.app/api/markets/984442)
[PolymarketTrade] Featured market anchor URL for market 984442 - 2026-02-25. [Open source](https://www.polymarkettrade.app/?view=featured#market-featured-984442)

FAQ

How is probability calculated in this market?

In a binary contract, YES price maps to market-implied probability on a 0 to 100 scale. The value is a live quote under current liquidity conditions, not a certainty statement.

Why is this article in fail-closed mode for external context?

Because we could not verify the required minimum of event-specific external sources for factual claims at publication time. The article therefore focuses on market mechanics, scenario triggers, and execution discipline.

Can a 69.5% YES market still move sharply in both directions?

Yes. Geopolitical contracts can reprice quickly when new information arrives, especially if depth is uneven. Directional conviction and execution quality are separate variables.

What is the main execution risk in this setup?

Slippage during fast windows when spread widens or near-touch depth thins out. Execution quality can diverge materially from headline card values.

What should be monitored as the deadline approaches?

Monitor time-to-resolution, spread stability, depth persistence by side, and whether repricing is sustained or repeatedly mean-reverts. Those factors usually matter more than isolated prints.

Bottom line

Current market signal is YES-leaning (69.5%), but this remains a live tradable quote rather than outcome proof.
This analysis is intentionally fail-closed on external event claims and limits itself to verifiable market data plus structured uncertainty.
If you agree with the YES case, monitor whether upside repricing is accompanied by stable spread and persistent depth.
If you agree with the YES case, monitor whether timing discount continues to shrink as the contract window advances.
If you agree with the NO case, monitor whether evidence-light spikes continue to fade after liquidity normalizes.
If you agree with the NO case, monitor whether time decay and deeper NO-side liquidity gradually dominate.