The MultiversX public blockchain mainnet has been suspended following an attack, with officials advising users to temporarily refrain from deposits and withdrawals while repair plans are being prepared. The incident constitutes a public chain-level security event that directly impacts user asset safety, and the progress of the fix and details of the attack have drawn market attention.
Mainnet suspended after attack; officials confirm repairs are being prepared
The MultiversX public blockchain has suspended operations after its mainnet came under attack. Following the incident, the project team issued a security notice explicitly advising users to pause deposits and withdrawals until the network returns to normal, while confirming that a repair plan is being prepared. The event has been classified as a public chain-level security incident. Not only did the attack halt mainnet operations, it also placed direct pressure on the safety of on-chain user assets. As of now, no further details have been disclosed regarding the specific attack method, the scope of impact, or the timeline for restoration, and the market is awaiting further official announcements. A public chain mainnet being attacked and suspended ranks among the more severe security contingencies in the crypto industry. Because public chains carry large amounts of on-chain capital and application ecosystems, any anomaly in the mainnet quickly transmits to affiliated users and ecosystem projects. The official prompt response following the incident reflects a clear assessment of the severity and provides necessary buffer time for subsequent handling.
Public chain mainnet outage: infrastructure role takes a direct hit
As a public chain project that has already launched its mainnet, MultiversX's mainnet serves core infrastructure functions in the overall architecture, including transaction processing, block production, and network consensus. The direct suspension of the mainnet means the underlying processing capacity of the chain has temporarily ceased, and all on-chain interactions relying on the mainnet cannot proceed normally. Unlike application-layer security incidents such as DeFi protocol attacks or smart contract exploits, a public chain mainnet-level event affects the entire chain, spanning multiple underlying components such as node operation, transaction confirmation, and asset settlement. Within the category of crypto security incidents, this ranks as a high-severity, hard-to-handle event that delivers a significant blow to ecosystem operations and user confidence. Such an infrastructure-layer outage typically means a period of operational disruption for the public chain ecosystem, and related applications and service providers will need to re-verify the integrity of on-chain data after the network is restored.
Official activates emergency response, suspends deposits and withdrawals, and advances repairs
Based on disclosed information, the MultiversX team quickly activated its emergency procedures after the attack. The mainnet suspension is a key step in this round of emergency measures, with the direct objective of cutting off the attack chain and containing further expansion of risk. Meanwhile, the team issued clear guidance to users via announcement: do not make deposits or withdrawals until the mainnet is restored. This guidance reflects a prudent approach to risk management, meaning that user fund channels will remain closed until the technical team completes repairs and confirms the network is secure, so as to avoid generating new on-chain state changes during the handling phase. Work on the repair plan is progressing in parallel. For a public chain project, restoring mainnet operations typically involves a series of technical steps such as node state synchronization, on-chain data verification, and network security hardening, and the entire process can only conclude with the network reopening after thorough security validation. At this stage, the key action users can take is to monitor official announcements closely and avoid any on-chain fund operations until repairs are complete, in order to prevent unnecessary risk exposure amid network uncertainty.
Public chain-level attack triggers chain-wide halt; asset safety becomes the focus
From an impact perspective, this is an attack that covers the entire mainnet. As the underlying infrastructure of the crypto ecosystem, a public chain's security and availability directly determine the security boundary for upper-layer applications, wallet services, trading platforms, and user assets. After the mainnet attack, the processes of transaction packaging, broadcasting, and confirmation were all interrupted, and normal calls to on-chain applications ceased, leaving the entire network's service capacity in a state of stagnation. This chain-wide halt means that any value transfer and business interaction relying on the public chain cannot be executed, and the scope of impact far exceeds that of a single application or business module. Asset safety is the most closely watched aspect of this event. With the mainnet suspended, users cannot initiate transfers or transactions through on-chain means, and asset liquidity is temporarily frozen. If the attack caused damage to on-chain state data, the repair process will also involve verification, rollback, or reconstruction of state data, which are technically complex operations that typically require careful execution. It is based on this conservative assessment of potential risks that the team chose to suspend the network and guide users to stop deposits and withdrawals, with the goal of maintaining on-chain state stability during the handling phase and creating conditions for subsequent repairs.
Security incident reflects industry challenges; public chain trust system tested again
Public chain security is the foundational support of the entire crypto industry's trust system. A public chain-level attack not only tests a project team's comprehensive capabilities in security protection, emergency response, and risk management, but also reflects the common challenges the industry faces when dealing with infrastructure-level attacks. The attack on MultiversX's mainnet and its forced suspension once again pushes public chain security issues to the center of market attention, providing the industry with a security case study worth reviewing in depth. For the industry, the lesson from public chain security incidents is that a network's resilience against attacks, the completeness of its emergency response plans, and the transparency of information during incident handling are all important dimensions for measuring the maturity of a public chain project.
Repair progress and impact assessment are the key items to track going forward
At this stage, the core focus of the event centers on two main lines: repair progress and impact assessment. On the repair front, the key question is whether the official technical team can advance the mainnet restoration as planned and whether the network will operate safely and stably after reopening. On the impact assessment front, key items include the specific scope of damage caused by the attack, whether user asset ledgers remain intact, and conclusions on the attack method and root cause of the vulnerability. The gradual clarification of these matters will determine the future trajectory of this incident, and these are the substantive developments users and the market most need to track at this stage. In addition, the efficiency and transparency of communication between the team and users during the handling process will also directly affect external assessments of the project team's trustworthiness. Until further official disclosure is made, judgments should remain cautious and should be based on official information.