US reports 13th consecutive night of strikes on Iran; Polymarket prices a ceasefire by month-end at 17%

At 04:10 UTC on 24 July 2026, citing the US military, Reuters reported that American forces had completed a 13th consecutive night of strikes on Iran. Twenty-eight minutes later, at 04:38 UTC, Middle East Eye's live blog reported that two people had been wounded by a US drone strike in Khorramabad, a city in western Iran. Two further data points from the same 24-hour window sharpen the picture. Polymarket, at 20:05 UTC on 23 July, priced a US-Iran ceasefire by the end of the month at 17% on one market question. Earlier the same day, at 15:05 UTC, a separate Polymarket question tracking an "effective ceasefire between U.S. and Iran" by the end of the month printed 16%. The headline of the Middle East Eye live thread on 24 July names a peace accord signing set for Friday in Geneva as the next scheduled event.

The most natural reading of the overnight sequence is that the air campaign and the diplomatic channel are running on parallel tracks. A 13-night strike rhythm is consistent with operations designed to degrade specified targets while a political track stays live. Monexus assessment: the strikes are doing diplomatic work in addition to whatever direct effect they have on Iranian targets. That assessment is, by construction, a judgment on incomplete information. The thread evidence names a strike, a tally, and two market prices, and stops there.

The 13th night, and the city that was hit

Reuters reported the 13th consecutive night of strikes on the authority of the US military. Middle East Eye reported two wounded in Khorramabad, Iran, from a US drone strike. The available source items do not specify the platform beyond the drone-strike designation, the targeted site, the identity of the wounded, or the extent of their injuries. They also do not specify whether any Iranian counter-action occurred in the same overnight window. The combined picture is of an air campaign that has now run for two full weeks without a publicly reported interruption, and that continues to produce at least one named casualty event per reporting cycle.

The two Polymarket questions

Polymarket priced a US-Iran ceasefire by the end of the month at 17% in a post at 20:05 UTC on 23 July. Earlier the same day, at 15:05 UTC, a separate Polymarket post priced an "effective ceasefire between U.S. and Iran" by the end of the month at 16%. The two posts track different market questions; the thread evidence does not establish that one is the prior tick of the other. The directional signal both questions ask is the same one: whether the fighting stops before the calendar turns to August. Monexus assessment: at 17%, the market is treating a month-end ceasefire as a real possibility but not the base case, which is consistent with a conflict that is being simultaneously prosecuted and negotiated.

What the headline says, and what the wire has previously said

The Middle East Eye live blog headline dated 24 July 2026 frames the next event as a peace accord signing set for Friday in Geneva. The available source items do not contain a first-party US or Iranian government confirmation of that signing, do not specify the venue within Geneva, the format, the principals who would attend, or the text of any framework agreement. The thread evidence, read carefully, supports a narrower claim: that a Geneva signing is the next scheduled item on the Middle East Eye live thread as of 24 July 2026, and that no other source in the present set corroborates it.

That caveat matters because the headline language ("US and Iran confirm") sits in tension with the body of the live coverage, which the present thread does not excerpt. Monexus assessment: a single live-blog headline citing a Friday signing is a thinner basis than two governments publicly confirming the same fact. Until either Washington or Tehran puts out a first-party statement on the record, the signing remains a scheduled event rather than a confirmed one.

The structural pattern

The shape on the page is familiar from earlier coercive air campaigns: an operation runs long enough to degrade specified targets, while a parallel channel keeps a diplomatic outcome available. The American side keeps the ability to point at damage assessments as it walks into a room; the Iranian side gets the cover to accept terms it could not accept if its cities were not also being hit, because the alternative reads as worse. Both sides have reason to keep the strikes going until any signing text is inked, and to keep the talks going until the bombs stop. That is the logic of a campaign that runs 13 nights while a Friday ceremony is pencilled in. It is also a logic that can break: a high-casualty strike in a populated area, an Iranian retaliation against Gulf shipping or US bases, a change of government in either capital, any of which would unwind the timetable in hours.

The sources do not specify which of those scenarios the principals are privately preparing for. They show a campaign and a calendar, running on parallel tracks, with the strikes setting the price any signing will be signed at, if it is signed at all.

Desk note: Monexus reported the 13th-night tally and the Khorramabad wounding as separately sourced items and avoided adding geography, provincial capitals, or bilateral-confirmation claims that the thread does not entail. Where two Polymarket posts tracked different ceasefire questions, we kept them distinct rather than reading one as the prior tick of the other.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://www.middleeasteye.net/live/live-us-and-iran-confirm-peace-accord-signing-set-friday-geneva
• https://x.com/MiddleEastEye/status/2080512911122800687
• https://x.com/Reuters/status/2080505809012756566
• http://reut.rs/3T7dL4p
• https://x.com/Polymarket/status/2080383817840267639
• https://poly.market/qhjYx8q
• https://x.com/Polymarket/status/2080308395995738620
• https://poly.market/Rn5tApf