Will a 6.0+ earthquake occur in Chile by August 31?
Probability
28¢
1h
+0.0pp
24h
-6.0pp
24h Vol
$0.00
Liquidity
$88.82
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
20% 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
20% 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
LOW risk- End date
- Sep 3, 2026
- UMA status
- n/a
- Resolution source
- Primarythe first preferred magnitude, country attribution and timestamp of the event in questionTypeAmbiguous wording
- Market type
- Binary
- Wide spread (45.0¢) — liquidity risk on entry/exit.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 3 factors- 01Price move
Down 6pp over 24h
Now 28¢; flat in the last hour.
- 02Active signal
Resolution-risk observation firing
Spread is wide enough that intraday moves overstate any tradeable edge.
- 03Spread cost
Wide spread — 45.0¢
Bid-ask spread is wide enough that intraday moves overstate any tradeable advantage. Most of the headline pp move would be eaten by spread on a market order.
What to track next
- Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
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
- Sep 3, 2026
- UMA status
- n/a
- Resolution source
- Primarythe first preferred magnitude, country attribution and timestamp of the event in questionTypeAmbiguous wording
- Market type
- Binary
- Wide spread (45.0¢) — liquidity risk on entry/exit.
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 ambiguous wording source and whether it directly answers the market's resolution question.
Current evidence: https://earthquake.usgs.gov/earthquakes/search/
Contract wording
requiredExtract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.
Orrery verification task Will a 6.0+ earthquake occur in Chile by August 31? State: Illiquid — liquidity sensitive Need sources for: 1. Primary source: Confirm the primary ambiguous wording 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 Will a 6.0+ earthquake occur in Chile by August 31? 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
- Sep 3, 23:59 UTCScheduled resolutionLOW
Market resolves in 500.5h
- 03:29SignalLOW
Resolution risk
Spread is wide enough that intraday moves overstate any tradeable edge.
Price movement
-6.0pp over the last 24h, now 28¢.
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
5- 42¢-17.0
Will a 6.0+ earthquake occur in Japan by August 31?
Weather · Vol $330.00
- 34¢-18.0
Will a 6.0+ earthquake occur in Indonesia by August 31?
Weather · Vol $60.52
- 41¢+4.0
Will a 6.0+ earthquake occur in the Philippines by August 31?
Weather · Vol $1.3K
- 21¢+5.5
Will a 6.0+ earthquake occur in Mexico by August 31?
Weather · Vol $71.01
- 21¢-35.5
Will a 6.0+ earthquake occur in the United States by August 31?
Weather · Vol $280.00
Market Description
This market resolves to "Yes" if the United States Geological Survey (USGS) reports an earthquake with a preferred magnitude of 6.0+ attributed to the listed country, with an origin time between market creation and the end of the listed month (UTC), by the end of the third calendar day after the specified month (UTC). Otherwise, that market resolves "No". A qualifying earthquake must be counted for a country's market only if USGS attributes its location to that country (or its offshore territory) in the event's location description, lists the earthquake with a preferred magnitude of 6.0 or higher, and lists it as occurring within the specified timeframe. Earthquakes without a preferred magnitude classification will not qualify. If an earthquake with an origin time within a market's window has not yet appeared on the resolution source by the end of the third calendar day after the specified month, this market end date may be extended for up to one week after the specified month and will resolve based on the first preferred magnitude, country attribution and timestamp of the event in question. If the relevant data is not released by the end of the extension period, this market will resolve based on the data released up until that point. Revisions to the underlying data, such as country attribution and preferred magnitude, will be considered until the end of the third calendar day after the specified month or until the end of an applicable extension period. Revisions made after the end of the third calendar day after the specified month or after the end of an applicable extension period will not be considered. The resolution source for this event is the United States Geological Survey (USGS) Earthquake Hazards Program earthquake catalog (https://earthquake.usgs.gov/earthquakes/search/), and only data released by USGS will be considered, regardless of other sources. If the resolution source becomes temporarily unavailable, the market will remain open until it resumes; if it remains unavailable through the end of the third calendar day after the specified month, this market will resolve to "No."
Why this category?
confidence: mediumCategory
Source
Matched term
earthquakeReason
Question text contains "earthquake" — matched the Weather keyword 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 "Will a 6.0+ earthquake occur in Chile by August 31?"?
As of Fri, 14 Aug 2026 03:29:12 GMT, YES is priced at 28% implied probability on Polymarket. The price changed -6.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 Sep 3, 2026 (2026-09-03T23:59:00.000Z). Resolution is determined from https://earthquake.usgs.gov/earthquakes/search/.
What source determines the outcome?
Resolution is sourced from https://earthquake.usgs.gov/earthquakes/search/. 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?
$0.00 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $141.98. Open liquidity in the YES/NO orderbooks: $88.82. Spread between best bid and best ask: 45.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.