MANTRA Chain Restarts, but Exchange Transfers Still Lag

---

MANTRA Chain resumed block production after deploying its patched v8.4.0 software release, restoring the mainnet after the Aug. 20 halt. Some exchange funding gateways remain restricted, however, and MANTRA has not yet published its full incident report.

Restarting the network restored its ability to process transactions, but recovery across connected services remains uneven. MANTRA’s status page was still marked as monitoring on Aug. 24.

What changed with version 8.4.0?

MANTRA Chain resumed block production at approximately 05:30 UTC on Aug. 22, roughly 30 hours after the network halted on Aug. 20, according to MANTRA. Validators restarted the mainnet using v8.4.0, which patches the vulnerability in MANTRA’s EVM module, specifically its Cosmos-EVM component.

The planned restart sequence was carried out in stages. MANTRA’s own validators upgraded first, followed by partner validators. Standard nodes, public endpoints and archive services were then brought back online.

MANTRA reported that its public mainnet infrastructure was operational again after the software upgrade, although some connected services still required additional time to recover.

>>> Related: Mantra Chain Halted After Software Exploit

Were user funds at risk?

MANTRA has said no. The exploit was isolated to two wallets the project itself controls, not user wallets. The project stated it found no indication that user, exchange, or partner funds were affected. “No user funds were exploited,” the team said in its root-cause statement.

That does not mean every question about the incident is closed. MANTRA has not disclosed what happened inside those two wallets, whether any assets moved, or what the incident’s full financial impact was.

Separately, MANTRA reported no rollback and no change to the ledger state between the halt and the restart. A rollback would mean reversing part of the chain’s transaction history, while the ledger state refers to the recorded balances and other data held by the network. According to MANTRA, neither was rewritten during the restart, and user balances were not altered. Token holders do not need to take action.

Why are some exchanges still restricted?

MANTRA can coordinate the recovery of its own network, but it cannot reopen exchange funding gateways itself. A funding gateway is an exchange’s infrastructure for processing deposits and withdrawals, separate from the blockchain. Each exchange must reconnect that infrastructure and complete its own operational checks before transfers resume.

Bitvavo continued to list MANTRA deposits and withdrawals as temporarily suspended when its status page was checked on Aug. 24. Trading remained available on the platform. Kraken’s status page continued to show delays affecting its MANTRA funding gateway.

Users can have different levels of access to the same network. A self-custody wallet, meaning a wallet where the user directly controls the assets instead of holding them through an exchange account, may already be able to interact with MANTRA Chain while an exchange customer remains unable to deposit or withdraw.

MANTRA said its public RPC and EVM endpoints were operational. These endpoints are the connection points that allow wallets and applications to communicate directly with the chain and submit or retrieve network data.

Why are explorers and indexers lagging?

Some explorers, indexers and other downstream services may continue to lag while processing the backlog created during the halt, according to MANTRA. Explorers are user-facing tools that display blockchain transactions and account activity, while indexers organize that network data so applications and interfaces can retrieve it efficiently.

These tools operate separately from the core validation process. The network can already validate a transaction, even if an explorer displays it late or an indexer has not yet processed the relevant data.

What does MANTRA still need to disclose?

MANTRA has not yet published its full incident report or post-mortem explaining the Aug. 20 security event and subsequent halt.

Further detail is still missing on the MANTRA-managed wallets referenced earlier, including what exactly occurred with these wallets and the final financial impact. The project has not named the specific upstream software component that contained the exploited weakness. Also the complete attack path remains undisclosed.

Separately, the DuKong testnet remained offline in MANTRA’s latest update, with restoration expected over the following days.

MANTRA said on X that a full post-mortem will follow in the next few days.