Ukraine strikes another vessel in the Black Sea by July 31, 2026?
Probability
36¢
1h
+0.0pp
24h
+0.0pp
24h Vol
$265.05
Liquidity
$487.96
Canonical status
confidence: mediumSource status (Polymarket)
Derived status (Orrery)
Reason
Liquidity is below $1,000 — price discovery is unreliable.
The derived status is computed from the source flags plus the live YES price, so a market trading near a rail can read as PRICE-PINNED while upstream is still active. That isn't the same as resolved.
Methodology explanation
Review-only opportunity
No paper intent is emitted from the public opportunity row. Paper action appears only after the paper governor evaluates the row.
Why this market is in review
signalResolution-source risk
40% source confidence on this opportunity row.
Paper-only action
paper-onlyReview-only opportunity
read_only_explanation; no live order, no network send, no raw secrets.
Risk / veto readback
reviewResolution review required
The public opportunity row has not passed the paper governor; source wording and settlement state remain review blockers.
Source evidence
source4 mapped surfaces
283/283 sources runtime-backed; all registered sources are runtime-backed; live authority remains false.
Signals
- Resolution-source riskwatch
40% source confidence on this opportunity row.
Veto / blockers
- Resolution review requiredwatch
The public opportunity row has not passed the paper governor; source wording and settlement state remain review blockers.
- Confidence below paper gatewatch
Paper policy needs at least 72% confidence before any paper intent can be proposed.
Costs / sizing
- Research score
- Composite opportunity score before paper-governor costs and vetoes.
- Capacity
- Estimated research capacity, not an approved size.
- Liquidity
- Market liquidity visible on the opportunity row.
all registered sources are runtime-backed; live authority remains false; this card cites mapped surfaces only.
Resolution & Risk
HIGH risk- End date
- Jul 31, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Binary
- Market expires Jul 31, 2026 — dispute window active.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 2 factors- 01Active signal
Resolution-risk observation firing
Expires in 66h.
- 02Liquidity
Thin liquidity
Only $488 of visible book — small orders can move the line. Treat the probability as a soft estimate.
What to track next
- Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
- Set an alert for resolution status changes — expiry is in 66 hours.
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
HIGH risk- End date
- Jul 31, 2026
- UMA status
- n/a
- Resolution source
- Primaryconsensus of credible reportingTypeNews consensusConfidenceextracted · medium
- Market type
- Binary
- Market expires Jul 31, 2026 — dispute window active.
Verification Brief
A guided checklist for what must be proven before this market is treated as reliable context.
Liquidity is thin enough that movement can be noisy. Verify source context before reading the move as information.
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 Ukraine strikes another vessel in the Black Sea by July 31, 2026? State: Illiquid — liquidity sensitive 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. 3. Liquidity context: Check whether the move is supported by enough liquidity and volume to treat it as meaningful context. Drop only durable links that map to one criterion. Research only. Not trade advice.
Orrery verification brief Ukraine strikes another vessel in the Black Sea by July 31, 2026? State: liquidity sensitive 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 31, 23:59 UTCScheduled resolutionHIGH
Market resolves in 65.7h
- 06:19SignalLOW
Resolution risk
Expires in 66h.
Price movement
+0.0pp over the last 24h, now 36¢.
Active signals
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
7- 0¢0.0
Strait of Hormuz traffic returns to normal by July 31?
Geopolitics · Vol $727.2K
- 34¢-14.6
US x Iran Effective Ceasefire by July 24?
Geopolitics · Vol $695.5K
- 100¢0.0
US announces halt in Iran offensive operations by July 31?
Geopolitics · Vol $692.9K
- 11¢-2.0
Strait of Hormuz traffic returns to normal by August 31?
Geopolitics · Vol $386.5K
- 39¢-15.5
US x Iran Effective Ceasefire by July 31?
Geopolitics · Vol $310.2K
- 0¢-0.1
Kharg Island no longer under Iranian control by July 31?
Geopolitics · Vol $272.6K
Market Description
This market will resolve to "Yes" if there is a strike against any vessel in the Black Sea attributed to Ukraine between market creation and the specified date, 11:59 PM Eastern European Time (EET). Otherwise, this market will resolve to "No". A "strike" is defined as the use of aerial bombs, drones, naval drones, naval guns, artillery, or missiles (including cruise or ballistic missiles) which impact a vessel anywhere in the Black Sea, regardless of flag, ownership, or damage level. Strikes attributed to Ukraine by media or third parties will qualify, regardless of whether Ukraine publicly denies involvement or if definitive attribution is not confirmed. Ship seizures, boarding, or the use of small arms fire will not qualify. An intercepted missile or drone that does not impact the vessel will not qualify, even if debris lands on or near the vessel. The primary resolution source will be a consensus of credible reporting. The occurrence, attribution, and timing of a qualifying incident will be primarily determined based on a consensus of information available from the resolution sources. Where multiple sources conflict regarding the occurrence, attribution, or timing of a relevant incident, this market will remain open until the earlier of: i) the confirmation of the occurrence, attribution, and timing of the incident based on a consensus of information available from the resolution sources or ii) 3 full calendar days (EET) from the date of the first credibly reported evidence of the incident. If this period would extend past the end date, this market will remain open to allow for 3 full calendar days to pass. If, at the end of the third calendar day, conflicting reports remain as to the occurrence, attribution, or timing of the incident, this market will resolve based on the totality of information available from the resolution sources at that time. No single statement, denial, or presentation of evidence will govern where it is contradicted by the totality of information.
Why this category?
confidence: highCategory
Source
Matched term
ukraineReason
Question text contains the high-signal keyword "ukraine" — 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 "Ukraine strikes another vessel in the Black Sea by July 31, 2026?"?
As of Wed, 29 Jul 2026 06:19:24 GMT, YES is priced at 36% implied probability on Polymarket. The price changed +0.0pp in the last 24 hours, +0.0pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Jul 31, 2026 (2026-07-31T23: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?
$265.05 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $265.05. Open liquidity in the YES/NO orderbooks: $487.96. Spread between best bid and best ask: 1.0¢.
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.