A9 PREDICT

A9 Predict

Changelog

Changes associated with this build.
v0.2.0Build identifier supplied

Build date · Eastern: Oct 25, 2026, 1:41:30.352 PM EDT

Technical build details
Commit
ef695042b6cc7b8d0132bc9eb2a0a1890d123d57
Version source
Running build metadata

Build metadata does not confirm production deployment or service health.

v0.2.0 This build

Keep this round's issued prediction readable, with a separate fresh entry comparison when matching evidence is available.

Added

  • One-contract entry estimate from matching fresh forecast, quote, depth and timestamped series fees; no orders are placed.
  • Current Kalshi round, threshold, close countdown and timestamped public quotes, separate from immutable A9 forecasts.
  • Eastern-day count of unique rounds with acknowledged forecasts and saved settlement status; real trades remain unavailable without fills.

Fixed

  • Saved history stays historical, including records from an open round; it does not show a current pick or start quote refreshes.
  • An issued prediction stays visible until its round closes, with its original probability and an explicit stale-input label after freshness expires.
  • Invalid reference timestamps, conflicting records and different-round quotes cannot supply a selection or entry comparison.
  • Forecast-only pilots can use the approved budget while learning stays off.
  • Quotes retire when stale, closed, mismatched or incomplete; an old forecast is never relabeled as current.
  • Bounded response parsing and shared in-flight public reads prevent simultaneous viewers multiplying upstream work.

Changed

  • Target prices spell out At least versus Above from the contract comparison; original Kalshi wording and rules remain in Details.
  • Untracked no-pick counts and the absence of a trading connection are labeled explicitly instead of appearing as a temporary data outage.
  • Canonical ACE9 Living Glass theme, compact historical evidence, and Eastern Time throughout.
  • Accessible version dialog groups Added, Fixed and Changed notes for this exact build.
  • Page reads do not start forecast collection, learning or order execution.

Tracked question

Will Bitget resume withdrawals by September 27, 2026?

A9 gives this a 5% chance of happening. That's about the same as the betting market (4%). A9 researched this on the web before forecasting.

Market 4%Polymarket
A9 Predict 5%high confidence

Jev on its own said 8%

+1 pts vs market
Leans NO

Why A9 thinks this

The evidence, separated.

Web research · quality 75/100

Official Bitget statements and multiple credible reports confirm a large hot-wallet exploit on Sept 24, 2026 and that withdrawals were suspended while investigations, security hardening, and recovery efforts proceeded. Bitget committed to announcing a withdrawal plan by 04:00 UTC on Sept 26, and some media outlets report a phased resumption schedule beginning Sept 28 (UTC). There were no authoritative, platform-level indications in the cited reporting that withdrawals had been reopened before the market cutoff (Sept 27, 2026 23:59 ET). The key unknown is whether Bitget would implement any official, platform-visible partial resumption earlier than the schedules reported. ([bitget.com](https://www.bitget.com/support/articles/12560603896108?utm_source=openai))

For

Bitget publicly committed to publishing a withdrawal-resumption plan by 04:00 UTC on September 26, 2026 — a timeline that implies the company intended to decide on reopening quickly. ([bitget.com](https://www.bitget.com/support/articles/12560603896108?utm_source=openai))

Bitget and multiple reports stated the incident affected hot/warm wallets only, that cold wallets and private keys were not compromised, and that the vulnerability was patched — facts that make a phased/limited resumption technically plausible in a short timeframe. ([theblock.co](https://www.theblock.co/news/markets/2026-09-24-more-than-170-million-in-crypto-moves-from-bitget-wallets-unidentified-address-416345?utm_source=openai))

Bitget launched an asset-recovery bounty, published attacker addresses and tracking dashboards, and received offers of assistance from other major exchanges and ecosystem participants — actions that could accelerate recovery and safe resumption of withdrawals. ([finance.yahoo.com](https://finance.yahoo.com/markets/crypto/articles/bitget-hack-timeline-own-system-164015015.html?utm_source=openai))

Against

Bitget suspended withdrawals on Sept 24 and repeatedly stated withdrawals remained suspended while security reviews and recovery efforts continued; as of the latest official updates cited, withdrawals had not been reinstated. ([bitget.com](https://www.bitget.com/support/articles/12560603896108?utm_source=openai))

Independent reporting and local crypto media published a phased resumption schedule that begins on September 28 (UTC) for major chains (e.g., BTC on Sept 28), which is after the market’s cutoff (Sept 27 23:59 ET = Sept 28 03:59 UTC). If accurate, that schedule implies no resumption by the deadline. ([en.theblockbeats.news](https://en.theblockbeats.news/flash/369094?utm_source=openai))

Outside forensic and security involvement (Mandiant, SlowMist cited in reporting) plus on-chain tracing showing funds dispersed to many addresses increase technical and legal complexity; that complexity commonly delays reopening of CEX withdrawals beyond 48–72 hours. ([tokenpost.com](https://www.tokenpost.com/news/technology/24028?utm_source=openai))

At the time of these reports there were no corroborated, platform-level indicators (official Bitget site/status or exchange UI) showing withdrawals had been made available before the forecast cutoff; isolated user claims alone do not meet the market’s resolution rule. ([bitget.com](https://www.bitget.com/support/articles/12560603896108?utm_source=openai))

Unknown

Whether Bitget will (or did) publish and implement an official, platform-visible resumption (even if partial/asset-limited) before 11:59 PM ET on September 27, 2026 — i.e., whether the company’s promised plan/controls would result in an actual platform state change before the deadline.

What would change A9's mind

  • Bitget posts an official platform/status update or UI change explicitly showing that withdrawals are available (any asset subset/partial scope) before 2026-09-28T03:59:00Z.
  • Bitget publishes a phased schedule with effective times earlier than reported (e.g., any asset re-enabled before 03:59 UTC on Sep 28). ([en.theblockbeats.news](https://en.theblockbeats.news/flash/369094?utm_source=openai))
  • Law-enforcement or on-chain freezes succeed in reclaiming a material portion of stolen funds very rapidly, allowing Bitget to authorize withdrawals sooner.
  • Bitget discovers additional severity (new outflows, new exploited assets, or further vulnerabilities) that extends suspension beyond the planned window.

Probability history

A9 never rewrites the past.

MarketA9Me
5%Initial read

Official Bitget statements and multiple credible reports confirm a large hot-wallet exploit on Sept 24, 2026 and that withdrawals were suspended while investigations, security hardening, and recovery efforts proceeded. Bitget committed to announcing a withdrawal plan by 04:00 UTC on Sept 26, and some media outlets report a phased resumption schedule beginning Sept 28 (UTC). There were no authoritative, platform-level indications in the cited reporting that withdrawals had been reopened before the market cutoff (Sept 27, 2026 23:59 ET). The key unknown is whether Bitget would implement any official, platform-visible partial resumption earlier than the schedules reported. ([bitget.com](https://www.bitget.com/support/articles/12560603896108?utm_source=openai))

a9-predict-0.3.0 · 3ade3109e6db84a1a3e64d343f6b3d9f78a949536e91feb64f9aab05833d3501