Will Kai or Speed be eliminated by a cactus?
Probability
4¢
1h
+0.1pp
24h
-1.4pp
24h Vol
$215.15
Liquidity
$72.10
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
5% 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
5% 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
- Aug 31, 2026
- UMA status
- n/a
- Resolution source
- Market type
- Binary
- Wide spread (5.5¢) — liquidity risk on entry/exit.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 3 factors- 01Price move
Down 1pp over 24h
Now 4¢; +0.1pp in the last hour.
- 02Active signal
Resolution-risk observation firing
Resolution source is ambiguous or relies on public-figure statements — verify before treating price as the market view.
- 03Spread cost
Wide spread — 5.5¢
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
- Aug 31, 2026
- UMA status
- n/a
- Resolution source
- Market type
- Binary
- Wide spread (5.5¢) — 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://www.youtube.com/watch?v=Sm9Af2DPsqs
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 Kai or Speed be eliminated by a cactus? 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 Kai or Speed be eliminated by a cactus? 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
- Aug 31, 23:59 UTCScheduled resolutionLOW
Market resolves in 542.5h
- 09:28SignalLOW
Resolution risk
Resolution source is ambiguous or relies on public-figure statements — verify before treating price as the market view.
Price movement
-1.4pp over the last 24h, now 4¢.
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
6Market Description
Kai Cenat and IShowSpeed are scheduled to stream a hardcore Minecraft marathon on August 7, 2026, at 5:00 PM ET, in which they will attempt to defeat the Ender Dragon, the Wither, the Warden, and the Elder Guardian in a hardcore Minecraft world on Java Edition, on the same seed, without either player dying in-game. For the purposes of this market, "the marathon" refers to Kai and Speed's Minecraft stream beginning on that date and continuing until they conclude or abandon it. This market will resolve to "Yes" if a death message listed in the Java Edition section of https://minecraft.wiki/w/Death_messages (as that page appeared at market creation) for the specified damage type is displayed for either Kai or Speed following an in-game death during the marathon. Otherwise, this market will resolve to "No". Every death message listed for that damage type will count. The category of the in-game death is what matters, not the mob or player involved. Death messages listed for any other damage type on that page, or under the Bedrock Edition section, will not count, even where the cause of in-game death appears related. A death message produced by any means other than an actual in-game death, including chat messages, overlays, or messages triggered by commands, will not count. Only one qualifying in-game death is required, and it may be by either player. This market will resolve to "Yes" immediately upon a qualifying in-game death. Only in-game deaths of the two accounts played by Kai Cenat and IShowSpeed will count. In-game deaths of any other player in the world, including guests, moderators, or co-streamers playing on their own accounts, will not count. It does not matter who is physically at the controls when an in-game death occurs; only whose account died in-game. Deaths in any Minecraft world played as part of the marathon will count, including restarts on new seeds, and including if Kai and Speed modify or abandon the objectives of the challenge, change the ruleset, or play outside of Hardcore mode at any point. No in-game death will count if it occurs while the player in question is in Creative or Spectator mode, or if it results from the use of commands, cheats, or any external tool to spawn entities, alter the world, or deal damage. Only in-game deaths occurring while at least one of the two players is broadcasting the marathon live will count. Footage of off-stream or previously recorded attempts will not qualify. This market will remain open until the marathon ends, regardless of whether the challenge is completed. If the marathon ends without a qualifying in-game death, or if the marathon is cancelled or never begins, this market will resolve to "No". If the marathon is still ongoing as of September 30, 2026, 11:59 PM ET, this market will resolve based on in-game deaths that have occurred up to that time. The resolution source for this market will be footage from the official broadcasts of the marathon on Kai Cenat's and IShowSpeed's official broadcasts on YouTube and Twitch.
Why this category?
confidence: lowCategory
Source
Reason
No override, sports marker, rule, or upstream hint matched. Market is unclassified — the keyword rules need an entry for this topic.
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 Kai or Speed be eliminated by a cactus?"?
As of Sun, 09 Aug 2026 09:28:11 GMT, YES is priced at 4% implied probability on Polymarket. The price changed -1.4pp in the last 24 hours, +0.1pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Aug 31, 2026 (2026-08-31T23:59:00.000Z). Resolution is determined from https://www.youtube.com/watch?v=Sm9Af2DPsqs.
What source determines the outcome?
Resolution is sourced from https://www.youtube.com/watch?v=Sm9Af2DPsqs. 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?
$215.15 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $434.59. Open liquidity in the YES/NO orderbooks: $72.10. Spread between best bid and best ask: 5.5¢.
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.