MANTRA switched its blockchain back on early on August 22. The freeze had run about 28 and a half hours, every validator and relay stopped after what the team described as an incident in the Cosmos EVM module. A patched build, version 8.4.0, shipped to mainnet and blocks started flowing again. The postmortem MANTRA promised when it pulled the plug still has not arrived.
When the chain went dark on August 20, MANTRA said no user, exchange, or partner funds were affected, and that only two company-managed wallets were touched. It never named an amount. The team pointed at the Cosmos EVM module, the same component that cost the Saga network about $7 million in January through a known precompile bug. We laid out that timeline when the halt first hit, in the module MANTRA chose to blame.
What version 8.4.0 actually changed
The patched code is live. Reading what it fixed is another matter, because the team has not explained the flaw it closed. According to CryptoSlate, the recovery upgrade blocklisted a single address and switched off three Cosmos vesting-account creation message types through a circuit breaker. The release tag was re-pushed mid-recovery, with node operators told to pull it again. Those notes cover the patch while saying nothing about the attack that forced it. The wallet addresses, the transaction hashes, the amount that moved, and whether this was January's precompile flaw returning are all still blank.
| Item | Status as of August 28 |
|---|---|
| Chain restart | Live, version 8.4.0, roughly 28.5 hour halt |
| Address blocklisted | One, not identified |
| Functions disabled | Three vesting-account message types |
| Amount moved | Not disclosed |
| Wallets affected | Two company-managed, not named |
| Attack path | Not disclosed |
| Postmortem | Promised, not published |
Blocks and withdrawals are two separate switches
A running chain does not mean money moves. Blocks resumed on August 22, and withdrawals stayed frozen for hours after that. Binance kept OM deposits and withdrawals on Mantra Chain suspended, and paused BEP20 withdrawals as well, telling users it did not want assets stuck mid-transfer. The exchange gateway and the network are separate systems, and the second one lagged the first by most of a day. For a holder trying to move OM off an exchange, the chain being live was not the part that mattered. Recoveries like this get judged on what the team publishes afterward, the way the Resolv team walked through its 72-hour scramble, not on how fast a node restarts.
OM was already broken before any of this
None of this landed on a healthy token. OM trades near $0.0043, a market cap around $27 million and a fully diluted value under $35 million. It sits roughly 84% below its March high of $0.0263, the level it reached after MANTRA migrated the chain earlier this year. The deeper wound is older. In April 2025 OM lost close to 90% of its value in a few hours and wiped out more than $5 billion, a collapse that still colors how traders read every MANTRA disclosure. A project that sells itself on real-world-asset infrastructure has now frozen its chain and shipped a patch it will not explain, with the details still blank a week later. Whenever the postmortem lands, it will have to account for more than this week's halt.
