MANTRA chain resumes after 28-hour halt as Binance freezes OM withdrawals

OM holders on Binance still could not withdraw 15 hours after the MANTRA chain resumed block production.

MANTRA's blockchain resumed block production at 03:38 UTC on Aug. 22 after a 28-hour halt, yet Binance kept OM withdrawals frozen 15 hours later. The chain's public REST endpoint, queried with chain ID mantra-1 at 18:38 UTC on Aug. 22, showed blocks producing at a 3.32-second cadence — the network's normal rate — with the first block after restart carrying 301 transactions.

The exchange's own network endpoint at the same timestamp listed OM withdrawals as suspended, with a note that withdrawals were paused "to prevent assets getting stuck in processing." OM traded at $0.00456, or €0.00391, at 18:35 UTC, down 5.4 percent over 24 hours, with a market capitalization of about $28.8 million, per CoinGecko.

The gap between a running chain and a closed exchange gateway is the practical lesson. A chain halt preserves balances but freezes movement; an exchange adds a second switch that must be reopened separately. For holders, the difference decides whether they can reach their tokens at all.

A chain halt is an emergency switch, not an accident. Validators in the Cosmos ecosystem can agree to pause block production while a fault is investigated, freezing every deposit, withdrawal, and application on the chain. MANTRA halted its mainnet late on Aug. 20 after detecting an attacker exploiting a vulnerability in an upstream software dependency, later traced to its Cosmos-EVM module. The incident affected two MANTRA-managed wallets, and the project said user balances were unchanged, with no rollback of network state.

The standstill lasted 28 hours 25 minutes, measured precisely by block timestamps. The last block before the halt carried the timestamp 23:13:04 UTC on Aug. 20; the chain stopped at block 17,449,398. The restart came through version 8.4.0, tested on the DuKong testnet and internal rehearsal environments before validators received the signal to resume.

Network status and exchange status are two separate switches

An exchange runs a separate funding gateway for every token and network — the software that receives deposits from the blockchain and sends withdrawals out. When a chain stalls, the exchange shuts this gateway so no withdrawal gets stuck in transit. The switch does not flip back on its own once the chain runs again; the exchange must resync its nodes, reconcile deposit-address balances against the restored chain, and grant internal clearance.

That is why Binance's OM withdrawal field still read suspended at 18:38 UTC on Aug. 22, roughly 15 hours after the restart. The exchange's note said withdrawals were paused "to prevent assets getting stuck in processing and/or loss of funds," with no commitment on a reopening date. Deposits, by contrast, were declared safe once confirmed on the blockchain. The same token remained tradable elsewhere: Kraken's public asset endpoint listed OM as enabled at the same timestamp, and the exchange publishes deposit and withdrawal disruptions openly on a status page.

The BEP20 route offered no workaround. Withdrawal via BNB Smart Chain was likewise suspended, with the note "Withdrawal for this token is not supported, please try other networks," while deposits via that network were open. An open deposit route is no assurance the same route works in reverse.

Self-custody removes the second switch

The incident draws a clean line between self-custody and exchange custody. In self-custody, a holder depends on the chain alone: if it runs, they can send in the same minute. In exchange custody, two conditions must hold at once — the chain running and the gateway open. Here exactly one was met.

The market priced the event in at the moment it happened. OM marked an all-time low of $0.00412644 at 23:09:10 UTC on Aug. 20, three minutes 54 seconds before the chain halted. The token fell 18.5 percent during the outage, with trading volume surging nearly 600 percent to about $24 million, per CoinGecko. By Friday afternoon it had recovered to near $0.005, close to its pre-halt level. The all-time high stands at $0.02627 from March 4, 2026.

The cause remains an attribution, not an established fact. CoinDesk called it an exploit in its headline; The Block described it neutrally as an incident. MANTRA said the vulnerability sat in its Cosmos-EVM module and affected two of its own wallets, with no user funds drained. Whether the same ICS20 precompile flaw disclosed by Cosmos Labs in March 2026 — which caused an estimated $7 million loss on Saga EVM — was involved has not been confirmed. A full post-incident report is expected in the coming days.

For holders, the practical takeaway is to check both statuses separately. A running block counter answers exactly one question: whether the chain accepts transactions again. Whether an exchange has reopened its gateway is a separate query, and one that decides when a balance becomes reachable.

This article is for informational purposes only and does not constitute investment advice.