MultiversX announced that its mainnet returned to service on Thursday, September 24, roughly five days after being halted due to an exploit. According to the project’s technical account @CodeMultiversX, a recovery upgrade was implemented, block production resumed, and normal network activity could proceed. The official gateway displayed a September 24 block timestamp following the all‑clear, confirming that the network was generating new blocks.
In contrast, Kraken’s latest notice regarding EGLD painted a different picture for its users. As of September 24, the exchange’s incident page still indicated cancel‑only trading, with deposits and withdrawals remaining suspended. Cancel‑only mode permits users to cancel existing orders but prevents new orders from being placed and blocks trade execution. Consequently, the network’s restart alone did not restore EGLD trading or transfers via Kraken.
MultiversX restart in stages
MultiversX noted on September 19 that an attempted exploit of a virtual‑machine atomicity flaw had produced invalid state changes, prompting a pause in block production. The September 24 technical update stated that engineering had finished recovery checks. The interval between the two dates suggests a disruption of about five days, although the exact moments of stoppage and resumption were not specified.
The timestamp recorded by the MultiversX gateway after the all‑clear aligns with the network’s report that block production had resumed. It does not indicate whether individual user transactions succeeded or whether trading platforms had restored their own services. @CodeMultiversX cautioned that trading, deposits, and withdrawals might stay halted on certain exchanges for several additional days while those platforms completed their reopening procedures. The network’s all‑clear applies only to the on‑chain environment; access through exchanges requires separate confirmation.
This distinction is important for anyone assessing which services are currently available. The network’s statement addresses whether on‑chain activity can resume, whereas Kraken’s notice governs the orders and funding channels it manages. A newly minted block does not remove an exchange’s trading restriction or confirm that the exchange is accepting deposits. @CodeMultiversX specifically advised users to consult their exchange’s official announcements before attempting to use those services. No update indicating a reopening time was present on Kraken’s incident page on September 24.
Kraken’s timeline of events actually precedes the network’s halt. The exchange first reported possible delays in EGLD funding gateways on September 16. By September 19, it had shifted EGLD trading pairs to cancel‑only mode and reiterated that deposits and withdrawals remained paused. Because the initial gateway warning arrived before MultiversX disclosed its exploit, the chronological overlap cannot be used to infer causation for Kraken’s original issue or its subsequent escalation.
For EGLD holders, the decisive indicator will be a Kraken announcement confirming the resumption of trading and funding capabilities. Until such a notice appears, MultiversX’s all‑clear merely restores on‑chain functionality, while Kraken’s ongoing restrictions continue to determine what its customers can do on the platform.