Zcash Orchard pool exploit confirmation stays a long shot at 6 percent

Name: Zcash Orchard pool exploit confirmation stays a long shot at 6 percent
Creator: ClearMarket
Published: 2026-09-30T00:00:00.000Z
License: https://creativecommons.org/licenses/by/4.0/

Polymarket 6%

record: CMSIG2026093007 | category: momentum-repricing | target: CM-EVT-96QBN5QTG3 | published: 2026-09-30

4-bullet brief | narrative

Polymarket puts only 6% odds on Zcash's Orchard pool being confirmed as exploited by January 1, 2027, treating the pool itself as likely intact.
Reports describe stolen funds being routed through Zcash's privacy pool, not a breach of the pool's cryptographic infrastructure -- a distinction the market appears to be pricing.
The news draws attention to privacy-coin exploit concealment mechanics without shifting the contract's probability, suggesting the market reads routing-through as distinct from a protocol exploit.
Resolution via UMA oracle requires confirmation that the Orchard pool itself was exploited, not merely used as a laundering channel -- a high bar given current reporting.

atomic briefs | structured for retrieval

[01] news_event

significance

surfaced in the daily Exa news-cycle scan; mechanically matched to an active polymarket market

story: Alleged North Korean hackers funneled approximately $3.8 million in Zcash stolen from cryptocurrency exchange Bitget through Zcash's privacy pool to obscure their trail after a $387.5 million exchange breach.exa_search → John Chen · as_of 2026-09-30T14:32:59+00:00
publisher: John Chen
published_at: 2026-09-30T00:00:00.000Z
source_url: https://cryptobriefing.com/bitget-breach-zcash-shielded-laundering/

[02] pm_response

interp: Polymarket contract at 6% resolves via UMA oracle on confirmation of an Orchard pool exploit specifically; laundering activity through the pool does not automatically trigger resolution.llm_judge_cm_signal_v1

evaluation

News-cycle wires publish on coverage, not editorial selection — the day’s top stories matched to the prediction markets pricing them, so nothing is cherry-picked.

judge_engine: none — deterministic news-cycle scan
judge_verdict: auto_published
judge_confidence: n/a — no judge gate (deterministic publishing)
prompt_template: news_cycle_v1 github · auditable
match_method: entity_slug_match (mechanical)

citation graph

Every wire traces back to the ClearMarket event it is built on, and out to each venue’s own market page — so any figure here can be verified at its source.

internal

cm_event: /events/zcashs-orchard-pool-confirmed-exploited-20260605210804589/

external

venue_a: polymarket · 0x270d3ef640f23a0908f7a3d477faf063baea28c8e2fd11d36f33b4f8c2ab4176

programmatic access · four surfaces, same payload

AI grounded search reads embedded JSON-LD in HTML. Developers query REST. Agentic AI clients (Claude Desktop, Cursor) call MCP tools. AI crawlers index via /llms.txt. Same canonical record at every surface.

HTML	browsers, AI grounded search, crawlers (contains embedded JSON-LD `@type: Dataset`)	`https://clearmarket.fyi/signals/zcash-orchard-pool-exploited-by-jan-2027-polymarket-6-2026-09-30/`
JSON	REST API for developers	`https://clearmarket.fyi/signals/zcash-orchard-pool-exploited-by-jan-2027-polymarket-6-2026-09-30.json`
MCP	agentic AI tool call (Claude Desktop, Cursor, Continue)	`clearmarket.get_signal("zcash-orchard-pool-exploited-by-jan-2027-polymarket-6-2026-09-30")`
AGENT	AI crawler discovery index	`/llms.txt`

 PM data: platform APIs (hourly refresh). News context: retrieved with source citations. Editorial judgment: LLM judge with prompt template versioned per wire type. Per-claim provenance inline above; full per-field provenance map at the JSON endpoint under field_provenance.
  raw JSON record · same payload returned by REST endpoint
 {
  "$schema": "https://clearmarket.fyi/schema/signal/v1.json",
  "provenance_version": "0.2.0",
  "record_id": "CMSIG2026093007",
  "published_at": "2026-09-30T00:00:00.000Z",
  "detection": "news_cycle",
  "category_tag": "MOMENTUM_REPRICING",
  "secondary_tags": [],
  "pre_news_classification": "concurrent",
  "target_event_id": "CM-EVT-96QBN5QTG3",
  "target_event_slug": "zcashs-orchard-pool-confirmed-exploited-20260605210804589",
  "event_question": "Will Zcash's Orchard pool be confirmed as exploited by January 1, 2027?",
  "bullets": [
    "Polymarket puts only 6% odds on Zcash's Orchard pool being confirmed as exploited by January 1, 2027, treating the pool itself as likely intact.",
    "Reports describe stolen funds being routed through Zcash's privacy pool, not a breach of the pool's cryptographic infrastructure -- a distinction the market appears to be pricing.",
    "The news draws attention to privacy-coin exploit concealment mechanics without shifting the contract's probability, suggesting the market reads routing-through as distinct from a protocol exploit.",
    "Resolution via UMA oracle requires confirmation that the Orchard pool itself was exploited, not merely used as a laundering channel -- a high bar given current reporting."
  ],
  "atomic_claims": [
    {
      "type": "news_event",
      "field_provenance": {
        "story": {
          "tier": "mediated",
          "method": "exa_search",
          "source": "John Chen",
          "source_url": "https://cryptobriefing.com/bitget-breach-zcash-shielded-laundering/",
          "retrieved_at": "2026-09-30T14:32:59+00:00"
        }
      },
      "significance": {
        "threshold": 5,
        "threshold_unit": "rank",
        "passed": true,
        "reason": "surfaced in the daily Exa news-cycle scan; mechanically matched to an active polymarket market"
      },
      "story": "Alleged North Korean hackers funneled approximately $3.8 million in Zcash stolen from cryptocurrency exchange Bitget through Zcash's privacy pool to obscure their trail after a $387.5 million exchange breach.",
      "publisher": "John Chen",
      "published_at": "2026-09-30T00:00:00.000Z",
      "source_url": "https://cryptobriefing.com/bitget-breach-zcash-shielded-laundering/"
    },
    {
      "type": "pm_response",
      "field_provenance": {
        "notes": {
          "tier": "editorial",
          "method": "llm_judge_cm_signal_v1"
        }
      },
      "notes": "Polymarket contract at 6% resolves via UMA oracle on confirmation of an Orchard pool exploit specifically; laundering activity through the pool does not automatically trigger resolution."
    }
  ],
  "evaluation": {
    "judge_engine": "none — deterministic news-cycle scan",
    "judge_verdict": "auto_published",
    "judge_confidence": null,
    "prompt_template": "news_cycle_v1"
  },
  "citations": {
    "internal": {
      "cm_event": "/events/zcashs-orchard-pool-confirmed-exploited-20260605210804589/",
      "related": []
    },
    "external": {
      "venue_a": null,
      "venue_b": null,
      "benchmark": null
    }
  },
  "sources": [
    {
      "label": "John Chen: Bitget funds reportedly shielded through Zcash after breach",
      "url": "https://cryptobriefing.com/bitget-breach-zcash-shielded-laundering/",
      "published_at": "2026-09-30T00:00:00.000Z",
      "retrieved_at": "2026-09-30T14:32:59+00:00"
    }
  ],
  "field_provenance": {
    "pm_data": "polymarket_api",
    "news_context": "exa_search",
    "editorial_judgment": "cm_signal_llm_judge"
  }
}
 
   PROVENANCE PROTOCOL v0.2 · [direct] venue api · [mediated] grounded web fetch + source url · [derived] computed from listed inputs · [editorial] versioned llm judgment · full spec /schema/provenance/v1

record CMSIG2026093007 published 2026-09-30T00:00:00.000Z signature sha256-fab41aa8c73… ← underlying event all signals →