TL;DR
- Mantra Chain halted after a software exploit, leaving transactions, transfers and staking unavailable while the network remains offline.
- A software patch is available, but restoring block production still depends on a coordinated validator upgrade.
- The company found no evidence that third-party user, exchange or partner funds were affected. The final financial impact remains undisclosed.
MANTRA Chain halted late on August 20 after an attacker exploited a vulnerability in the software used by the network. As of August 22, transactions, transfers and staking remain frozen, leaving users unable to move assets or change staking positions through the blockchain.
MANTRA has prepared patched software release v8.4.0, but installing and testing that fix has not yet brought the chain back online. The network remains unavailable while the project works toward a controlled restart across its validators.
What is MANTRA Chain?
MANTRA is a Layer 1 blockchain: it runs its own independent network for recording and processing transactions, instead of building on top of another blockchain. It focuses on bringing traditional assets, such as funds and bonds, onto that network, where ownership and transfers can be tracked directly.
>>> Read more: DAMAC & MANTRA’s $1B Blockchain Asset Tokenization Deal
What caused MANTRA Chain to go offline?
The network stopped producing new blocks at height 17,449,398 at about 23:13 UTC on August 20. MANTRA publicly announced the stoppage roughly 30 minutes later.
Public network endpoints, bridge connections to other blockchains and validators all went offline as part of the outage. Validators are the network’s operators, responsible for processing and confirming transactions.
MANTRA traced the incident to an upstream dependency, software that the project uses but did not develop itself. The vulnerable component was part of MANTRA’s EVM module, which allows applications built for Ethereum-style systems to run on MANTRA.
The project said it identified the root cause and reviewed known attack routes before preparing a software fix. MANTRA has not yet published a full technical post-mortem explaining the incident in detail.
Were user funds affected?
MANTRA’s status updates say the exploit affected two wallets managed by the project. The company says it found no evidence that third-party user, exchange or partner funds were affected.
But the assurance falls short of a complete financial accounting. Wallet balances, the full movement of funds, and the incident’s final financial impact all remain undisclosed so far.
How did the price react?
MANTRA’s token fell 18.5% to a reported record low shortly before the blockchain stopped producing blocks.
The timing places the market decline close to the network incident, but the sequence alone does not show that the exploit caused the price move. MANTRA has not established a direct connection between the two events.
Why hasn’t the patch restarted the chain?
MANTRA prepared version v8.4.0 to address the vulnerable software and add further security controls. The GitHub release is currently marked as a pre-release, meaning it has not yet been designated as a final version fully verified for normal production use.
The project tested the software in an internal environment designed to reproduce the mainnet’s existing condition and on DuKong, MANTRA’s test network. According to MANTRA, the upgrade does not require a state migration. In practical terms, the chain’s stored data does not need to be rebuilt or transferred into a new format. Operators mainly need to replace the affected software.
Upgrading one machine alone is not enough. The chain halted across MANTRA’s distributed network whose operators need to run compatible software and agree on the same transaction history. Restarting only part of that network could leave operators on different software versions or prevent reliable block production.
MANTRA therefore plans to coordinate the upgrade in stages. Its own validators are expected to update first, followed by partner validators. Standard nodes, public endpoints and archive services, which retain historical blockchain data, will follow once MANTRA confirms sufficient validator coverage
The software upgrade itself should take only seconds once operators are ready, according to MANTRA. The larger task is ensuring that enough independent participants have installed the patched version and can restart together safely.
What happens next?
MANTRA has not shared a specific timeframe for when it expects to resume operations. The project says it will give the go-signal after it has sufficient validator coverage and completes its final security review.
Users do not need to take action while the network remains paused. MANTRA has also warned holders to ignore people claiming they can help recover assets or resolve problems related to the outage, since impersonators may use the incident to target users with scams.
