
MultiversX Prepares Hard Fork Recovery After Security Incident

MultiversX Prepares Hard Fork Recovery After Security Incident
WEEX View
- The main near-term variable is restart execution. The market should watch whether validator rehearsals on testnet and the development network lead to a clean mainnet recovery without further changes to the published plan.
- Exchange and bridge reopening will be a practical liquidity signal. MultiversX has already warned users not to access EGLD or ESDT through exchanges or cross-chain bridges until recovery is officially announced, so infrastructure normalization matters as much as the fork itself.
- Users also need clarity on the final scope of impact. The project has outlined the recovery path, but details on affected assets, any permanent losses, and the status of funds moving through third-party platforms remain the key unresolved items.
MultiversX said it plans a coordinated hard fork from known good checkpoints after what it described as an attack incident caused by an operational sequence error, adding that validators had contained the situation and that exchanges and cross-chain bridges would reopen in phases after the network restarts.
According to the project’s statement, the root cause of the incident was an operational sequence error rather than a still-undisclosed protocol failure. MultiversX said validators responded quickly and brought the situation under control, and it proposed a coordinated hard fork using known good checkpoints as the basis for recovery.
The project said the recovery process would first be rehearsed with validators on testnet and the development network. It also said the relevant code had been made public and that testing was still in progress. Until the recovery is officially completed, MultiversX told users not to submit or rebroadcast transactions.
MultiversX also said the attacker’s accounts had been identified and frozen on major exchanges, and that law enforcement agencies were involved. However, the statement did not specify which exchanges had frozen the accounts, which authorities were participating, or whether any assets had already been recovered.
The network’s operational guidance extended beyond on-chain activity. MultiversX said EGLD and ESDT should not be accessed through exchanges or cross-chain bridges before the official recovery notice, underscoring that the incident affects not only validator coordination but also third-party infrastructure connected to the chain.
Why It Matters
A coordinated hard fork for incident recovery is a high-stakes step for any blockchain because it tests validator coordination, exchange support, and user confidence at the same time. In this case, the recovery plan is not limited to patching code: it also depends on checkpoint selection, synchronized infrastructure action, and orderly reopening across trading venues and bridges.
The episode also highlights how security incidents can quickly spill into centralized market infrastructure. Even when a network says the situation is contained, exchange freezes, bridge restrictions, and law enforcement involvement can shape how smoothly assets move back into normal circulation once the chain restarts.
This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.
About WEEX View
WEEX View is a crypto analysis and intelligence hub, covering the latest in Web3, AI, and global markets. Get independent research and in-depth insights to stay ahead of market trends and trading opportunities.
Latest articles
MoreBasedApp Data Breach Exposes KYC Data and Wallet Links
BasedApp data breach reports point to exposed KYC records tied to wallet addresses, while key details on user count, backend access, asset impact, and remediation remain unresolved.
JPYC Explains Stablecoin Payment Competition to Japan's Fair Trade Commission
JPYC reportedly briefed Japan
Core Lightning v26.06.9 Fixes Payment and Throttling Bugs
Core Lightning v26.06.9 was released on 2026-10-07 with fixes for a 26.06.8 throttling regression, a payment shutdown edge case, and added configuration and authorization hardening.
DWF Maas BitGo London Claim Centers on $141 Million Dispute
DWF Maas is reported to have sued BitGo in London for $141 million over alleged early token sales, but no matching public court record, case number, or BitGo response has been identified.




