Root Cause Traced to Upstream Dependency Flaw
The preventive shutdown followed indications that an external actor attempted to leverage a security flaw present in an upstream software dependency. In response, project contributors took the network offline to safeguard existing state data and contain potential exposures.
Network operators recorded a comprehensive snapshot of the ledger state prior to beginning remediation steps. Early assessments confirmed that no funds were illicitly generated, extracted, or compromised during the incident.
Exchange Deposit Suspensions and Market Volatility
Because block generation remained paused, centralized cryptocurrency trading venues suspended all token deposits and withdrawals routed through the native blockchain.
Major platforms, including Upbit, implemented temporary transfer freezes. Internal order books on exchanges remained functional, allowing off-chain spot and derivative transactions to continue despite the network suspension.
Market sentiment reacted swiftly to the news. The native MANTRA token slid by roughly 10%, dropping from an intraday high of $0.00506 down to an immediate support level around $0.004126 before stabilizing near $0.00445.
Trading volume experienced a sharp surge exceeding 591%, topping $22.7 million as market participants adjusted positions. Concurrently, derivative markets recorded a notable increase in futures open interest, which climbed over 18% across prominent exchanges like Binance, Gate.io, and KuCoin.
Developers Test Patch v8.4.0 Ahead of Validator Coordination
To address the underlying software flaw, core developers created a targeted fix designated as version 8.4.0. Testing for the patch commenced on the DuKong testnet to verify system stability before initiating mainnet deployment.
Restoring full network functionality requires a synchronized software upgrade across the decentralized validator set once testnet validation concludes.
Project representatives urged token holders to remain cautious, reminding the community that no individual action is required and warning against unverified third-party recovery services during the operational hiatus. Network validators were instructed to keep mainnet nodes dormant until official restart protocols are finalized.
eabungana@gmail.com