MANTRA Chain, a proof-of-stake Layer 1 focused on real-world asset (RWA) tokenization, remained halted on Aug. 21 after the team disclosed that an attacker had exploited a vulnerability in an upstream dependency. With the mainnet paused, transactions, transfers, and staking operations are all unavailable.

The project identified the vulnerable software only as an upstream dependency. According to its official incident record, MANTRA is tracing the movement of funds, working with exchange partners, and continuing to assess the complete scope of the incident.

The record lays out the sequence of events: MANTRA first froze endpoints and transactions while reviewing the root cause and impact. The team later attributed the precautionary halt to an attacker exploiting the upstream dependency, then announced a patched release along with testnet testing, with the mainnet staying offline throughout those updates.

In its latest update, the project said user funds were unaffected by the halt itself and that a full network state snapshot was taken before the restart process began. That assurance applies only to the network pause, which prevents transactions from being processed; the asset impact of the attacker's activity remains unconfirmed.

Patch testing gates the restart

MANTRA said patched release v8.4.0 addresses the underlying vulnerability and is undergoing testing and due diligence on the DuKong testnet. The project's GitHub release confirms the version and includes a mainnet upgrade handler.

Testing on DuKong serves as the gate before the same software is rolled out to mainnet. MANTRA said it is prioritizing a careful, verified rollout and instructed validators to keep their mainnet nodes offline until it announces a coordinated restart.

The coordination requirement prevents individual node operators from restoring mainnet service independently. Validators must wait for MANTRA's restart announcement so the patched network can return through the wider validator set together. That model matches how chains built on the Cosmos SDK, the framework MANTRA uses, normally handle software changes: the validator set applies an upgrade in unison rather than node by node, and the upgrade handler referenced in the release is the mechanism that gates such transitions.

Halting a network outright after a security incident is an established, if blunt, emergency response in the sector, since a full stop blocks all transaction processing while a fix is prepared. BNB Chain took a comparable step in October 2022, suspending its network after a cross-chain bridge exploit and resuming block production only after validators coordinated around patched software.

The team was targeting a restart later on Aug. 21, subject to testing completing cleanly. Mainnet can come back only after the patch clears testing and the broader validator set is ready for the coordinated upgrade.

For users, the halt means ordinary on-chain activity cannot proceed. Assets cannot move on MANTRA Chain, staking operations are unavailable, and deposits and withdrawals for the token remained paused on affected venues, according to earlier incident updates. MANTRA said users did not need to take any action while the chain remained offline.

A restart announcement would resolve the immediate operational freeze, while MANTRA's assessment of fund movements and the incident's complete asset impact remains a separate issue to watch.

Source: CryptoNews