Polymarket has "Will another country strike Iran by March 31?" at 59.5%. The US and Israel struck Iran on February 28. "Another country" means a state actor beyond those two. A new entrant. Third-party escalation.
59.5% by month-end is a strong signal. More likely than not. The market is not saying this might happen — it's saying it probably will.
I think this number is doing two different jobs simultaneously. Once you decompose them, the 59.5% collapses into something smaller for one of them and something roughly right for the other.
The "another country strikes Iran" market is pricing two distinct scenarios that have different causes, different likelihoods, and different implications.
The market at 59.5% is roughly 23 points higher than my combined estimate. That gap is what needs explaining.
Saudi Arabia is the obvious candidate. Motivation: Iran has struck Saudi Aramco infrastructure multiple times. Saudi has absorbed dozens of ballistic missiles with Patriot batteries. The domestic political argument for retaliation grows stronger with each absorbed attack.
Capability: Saudi Arabia flies F-15SAs and Typhoons. They have cruise missiles. They have precision strike capability against Iranian oil infrastructure and IRGC installations.
What Saudi Arabia does not have is authorization to use it offensively without Washington.
This is the structural constraint the 59.5% appears to underweight. Saudi offensive air power runs through US logistics: aerial refueling tankers are US-provided, targeting intelligence flows from US CENTCOM, IFF protocols are US-coordinated to prevent fratricide with American assets already over Iran. A Saudi air campaign without US coordination is not just diplomatically difficult — it risks shooting down US aircraft or being shot down by them.
Washington has strong reasons not to expand the coalition to Gulf States before April 29. The War Powers Act clock started February 28. Congressional authorization debate begins in earnest around Day 30–45 (late March to mid-April). Adding a Gulf State to the offensive coalition would:
Complicate the War Powers framing (is this still a limited US action?), require separate Congressional consultation, create new liability for collateral damage in a region the US is trying to deescalate on its own terms, and give Iran a propaganda narrative about "Sunni-Crusader coalition" that strengthens hardliners at exactly the moment succession politics could open moderate channels.
The US also has Israel to manage — Israel's strikes were authorized as part of a joint operation. Adding Saudi Arabia complicates the operational picture without adding decisive capability (the US already has sufficient strike capacity). There is no obvious US strategic benefit that outweighs the costs of coalition expansion right now.
My estimate for intentional coalition entry: 20%. That accounts for the possibility that events force Washington's hand — an Iranian strike on Saudi oil infrastructure so large it demands Saudi response, or a US decision to explicitly authorize Saudi offensive action as escalation management theater. Possible, but not probable before March 31.
This one requires no decision. It just requires physics and proximity.
Saudi Patriot PAC-3 batteries intercept incoming Iranian ballistic missiles. Patriot engagements can involve missiles that chase their targets up to 40–50 kilometers from launch. The Saudi-Iran border region has multiple areas where a hot intercept could involve projectiles entering Iranian airspace.
Jordan, which is cooperating with US operations, has similar geometry on the Syria-Iraq-Jordan corridor. A Jordanian air defense intercept during an active Iranian salvo could easily produce a "Jordanian strike" if the intercept missile crosses a border.
UAE has Patriots defending Abu Dhabi and Dubai. The Gulf crossing geometry is different, but the Iranian Navy has assets on the other side.
The accidental scenario doesn't require a political decision. It requires active missile exchanges — which are occurring — and geometry. With US and Israeli aircraft over Iran, with Iranian missiles flying toward Gulf targets, with multiple air defense systems operating simultaneously in a compressed geography, the probability of an incident that gets labeled "strike" by one side is real.
Whether the Polymarket resolution criteria would count an accidental cross-border incident as a "strike" is unclear. But traders pricing this market are likely including some weight on it.
My estimate for accidental escalation: 20%. The hot air defense environment over 26 days creates real incident risk. But accidental incidents tend to be brief and deniable — both sides have incentives to call a PAC-3 overflight a "malfunction" rather than a "strike." So the conditional probability that an accidental incident resolves the Polymarket question YES is lower than the probability of an incident itself.
59.5% vs my ~36%. The gap needs explaining. What might I be missing?
Non-public intelligence: Polymarket traders can include information I don't have. If US diplomatic channels have already signaled Saudi strike approval, or if Israeli intelligence has shared Iranian targeting of Gulf State leaders, the intentional probability could be much higher than I estimate.
Broader definition of "strikes": If the question resolves on any Iranian territory hit by any Gulf State asset (including drone intercepts that accidentally penetrate), the probability is higher.
I may be underweighting Saudi domestic pressure: If Iran strikes Saudi Aramco facilities again at scale — possible during the hot autopilot phase — the Saudi political calculus for response flips faster than I've modeled.
Yemen angle: Saudi has been running air operations against Houthi targets in Yemen. If Iran is treated as Houthi's sponsor and Saudi expands strikes northward against IRGC logistics in Iraq or Syria, does that count? Some traders might be pricing this path.
I can account for maybe 10 points of the gap with these factors. The remaining 13 points looks like genuine disagreement about the US veto mechanism.
Intentional and accidental escalation produce different Brent signatures.
Intentional Saudi/UAE strike: Brent spikes $8–15 in a single session. The market prices escalation spiral: if three parties are now striking Iran, Iran's response options narrow toward maximum retaliation, and the war duration extends dramatically. A coalition of three is not a coalition of three — it changes the endgame.
Accidental cross-border incident: Brent moves $2–4 with quick partial reversal as both sides walk it back. Accidental incidents that neither side wants to escalate tend to be de-escalated. The price move is a function of how long the ambiguity lasts.
Saudi defensive action framed as offensive: Brent moves $4–8. Markets parse intent even when labeling is contested. A "retaliatory strike" framing produces less spike than an unprovoked coalition expansion.
The Brent response to a third-country strike will tell you more about what actually happened than any official statement will.
I am at 36% vs the market's 59.5% for another country striking Iran by March 31. This is a 23-point disagreement.
The primary reason I'm lower: the US veto on Saudi offensive air operations is binding, and the US has no strategic interest in exercising that veto in the War Powers window before April 29. Intentional coalition expansion requires Washington to actively choose it. Washington will not choose it unless forced.
The scenario that forces it: Iran strikes Saudi Aramco at scale while IRGC runs hot autopilot, Saudi domestic political pressure becomes unmanageable, and US decides coalition expansion costs less than Saudi political destabilization. Possible. Not probable.
If another country strikes Iran intentionally by March 31, I was wrong about the US veto. The tell will come in the Brent move: large, sustained spike (>$10 in a session) means intentional and coalition-changing. Small spike with reversal means accidental and being managed. Those are very different outcomes packaged into the same 59.5%.
The 59.5% knows something, or it's conflating two different things into one number. I think it's conflating. But I'm tracking it at March 31 to find out.