UnclassifiedExpires Aug 31, 2026
Creator

Will Kai or Speed die to a polar bear?

Probability

44¢

1h

+22.0pp

24h

+34.5pp

24h Vol

$245.58

Liquidity

$13.35

Research loop

Inspect detail

Read the move, holders, recent trades, source, and resolution risk before saving anything.

Canonical status

confidence: medium

Source status (Polymarket)

active

Derived status (Orrery)

ILLIQUID

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.

read_only_explanationpaper-onlysend false

Why this market is in review

signal

Resolution-source risk

20% source confidence on this opportunity row.

Paper-only action

paper-only

Review-only opportunity

read_only_explanation; no live order, no network send, no raw secrets.

Risk / veto readback

review

Resolution review required

The public opportunity row has not passed the paper governor; source wording and settlement state remain review blockers.

Source evidence

source

4 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.
2
Capacity
Estimated research capacity, not an approved size.
$500
Liquidity
Market liquidity visible on the opportunity row.
$13
Explanation packet2026-06-16.1
DecisionSignalsVetoes and capsCostsDriftShadow policyLearning statusAuthority
What can be learned
Source-to-runtime coverage283/283 runtime-backed0 unmapped

all registered sources are runtime-backed; live authority remains false; this card cites mapped surfaces only.

P32-Source-to-Runtime-Coverage-Matrix-v1semantic_risk_kernelmethodology_runtime_boundarypromotion_gate+3
live falsesecrets falsetraining falsenot advice

Resolution & Risk

LOW risk
End date
Aug 31, 2026
UMA status
n/a
Resolution source
Primary
the actual mob type that caused the in-game death rather than the name displayed in the death message
Type
Ambiguous wording
Market type
Binary
  • Wide spread (77.0¢) — liquidity risk on entry/exit.

Probability (last 7 days)

+0.0pp 7d
1007550250
41¢
Aug 7, 2026, 23:00 UTCAug 9, 2026, 09:44 UTC
updated 09:44:34 UTC·src:Polymarket CLOB·snap:snap_2026-08-09T09-44Z

Why did it move?

Structured · 3 factors
  • 01
    Price move

    Up 35pp over 24h

    Now 44¢; +22.0pp in the last hour.

  • 02
    Active signal

    Resolution-risk observation firing

    Spread is wide enough that intraday moves overstate any tradeable edge.

  • 03
    Spread cost

    Wide spread — 77.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.

Verification Brief

A guided checklist for what must be proven before this market is treated as reliable context.

liquidity sensitive
Trust transition

Liquidity is thin enough that movement can be noisy. Verify source context before reading the move as information.

Create trust-state alert

Verification goal

Map resolution-relevant sources to the exact criteria needed to avoid misreading price as settlement.

What needs proof

Primary source

required

Confirm 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

required

Extract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.

Telegram verification task

Orrery verification task Will Kai or Speed die to a polar bear? 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.

X verification thread

Orrery verification brief Will Kai or Speed die to a polar bear? State: liquidity sensitive Verify: Primary source + Contract wording Price is not settlement. Research only. Not trade advice.

Market link goes in reply

Guided source review

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

Confirm the primary ambiguous wording source and whether it directly answers the market's resolution question.

Research only · no price-only screenshots · no profit claims

Recent source checks

Pilot audit summary

Research only · Not trade advice · Every source maps to one criterion

Timeline

critical · price · trade flow

Critical

  • Aug 31, 23:59 UTCScheduled resolution

    Market resolves in 542.2h

    LOW
  • 09:44Signal

    Resolution risk

    Spread is wide enough that intraday moves overstate any tradeable edge.

    LOW

Price movement

+34.5pp over the last 24h, now 44¢.

updated 09:44:34 UTC·src:Polymarket CLOB·Polymarket Data

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.

updated 09:44:34 UTC·src:Polymarket Data

Market 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 containing the specified mob's name is displayed for either Kai or Speed following an in-game death during the marathon. Otherwise, this market will resolve to "No". Any death message containing the specified mob's name will count, including its plural and possessive forms, and regardless of how the mob caused the in-game death. The exact mob name must appear; a death message naming a different mob whose name contains the specified mob's name will not count. For example, an in-game death to a Wither Skeleton will not resolve "Skeleton" to "Yes," and an in-game death to a Cave Spider will not resolve "Spider" to "Yes." An in-game death seeming to be caused by the specified mob will not count if the mob's name does not appear in the death message. If a mob has been renamed, this market will resolve based on the actual mob type that caused the in-game death rather than the name displayed in the death message. 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. 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: low

Category

Other

Source

Default fallback

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 die to a polar bear?"?

As of Sun, 09 Aug 2026 09:44:34 GMT, YES is priced at 44% implied probability on Polymarket. The price changed +34.5pp in the last 24 hours, +22.0pp 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?

$245.58 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $275.58. Open liquidity in the YES/NO orderbooks: $13.35. Spread between best bid and best ask: 77.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

¢
Deliver

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.