AscendEX
Custody businesses run on trust. Any founder communication gap during a liquidity event triggers a bank-run, whether or not the balance sheet supports it.
AscendEX was a Crypto / Centralized Exchange startup founded in 2018 in Singapore. It raised $50M+ before collapsing in 2026 — 8 years of runway burned. IdeaProof's AI Failure Score: 63/100, driven by liquidity crisis compounded by unexplained founder silence. The shutdown affected employees, investors, and the broader Crypto / Centralized Exchange ecosystem. This case study breaks down the timeline, root causes, competitors that won, and replicable lessons for founders validating similar ideas today.
Why did AscendEX fail?
AscendEX failed in 2026 after 8 years of operation, losing $50M+ in raised capital. The root cause was liquidity crisis compounded by unexplained founder silence. Key lesson: Custody businesses run on trust. Any founder communication gap during a liquidity event triggers a bank-run, whether or not the balance sheet supports it.
2018 → 2026
$50M+
Crypto / Centralized Exchange
Singapore
IdeaProof AI Failure Score
What Happened: The Timeline
2018
AscendEX founded in Singapore. Positioned in crypto / centralized exchange.
2018-2020
Raises $50M+ from Polychain Capital, Alameda Research, Hack VC.
2025
Warning signs emerge: frozen alameda-linked assets on balance sheet.
2026
Shutdown announced. Root cause: liquidity crisis compounded by unexplained founder silence.
Root Causes
AscendEX (formerly BitMax) was a top-30 centralized crypto exchange founded in 2018 by Wall Street quants, backed by Polychain, Alameda Research (pre-collapse) and Hack VC. In July 2026 the exchange announced it would cease operations amid a liquidity crisis, with founder George Cao going silent for weeks while withdrawals stalled. The Alameda linkage (frozen assets from the 2022 FTX bankruptcy estate) had impaired AscendEX's balance sheet, and 2026 crypto market weakness compressed trading fees below operating costs. Users are being onboarded to competitor exchanges for asset migration; recovery is expected to be partial.
Causal Chain
This is our reading of the causal chain — separated from the verifiable facts above. Timeline dates, funding numbers and filings are facts (see methodology); root / proximate / terminal attribution is judgement based on public evidence.
A combination of demand-side, execution, and capital-market pressures that this record documents without isolating a single dominant driver.
- Frozen Alameda-linked assets on balance sheet
- Fee compression in crypto downturn
- Founder silence triggered bank run
- No regulator to broker orderly wind-down
2025: Warning signs emerge: frozen alameda-linked assets on balance sheet.
2026: Shutdown announced. Root cause: liquidity crisis compounded by unexplained founder silence.
Base rates
A single failure is an anecdote. These base rates give you the denominator — how common this outcome is across all startups matching AscendEX's profile. Sources are third-party; we do not restate them as our own claims.
of crypto/Web3 projects launched in the 2021 cycle were inactive or delisted within 24 months of peak market cap.
CoinGecko + Nansen dataset analysis (2023)of startups ultimately fail — including ~10% that fail in the first year and the rest across the following decade.
Startup Genome / CB Insights aggregate (2024)of new US employer businesses survive past their 10th year (Bureau of Labor Statistics BED series).
US Bureau of Labor Statistics — BED (2024)of Series A rounds ever graduate to Series B; the rest run out of runway or pivot without a follow-on.
CB Insights Venture Capital Funnel (2023)Key Lessons Learned
Frequently Asked Questions
Sources & Confidence
Every data point is tagged with its source type and our confidence in it. How we grade sources.
Could This Failure Have Been Prevented?
IdeaProof's AI validates market demand, competitive positioning, and business model viability in minutes — catching the exact issues that sank AscendEX.
Spotted a factual error?
Approved corrections are published in the public changelog with attribution.