MultiversX restarts after exploit halt, but Kraken still bars new EGLD trades

MultiversX, a blockchain network, said its mainnet was back online Thursday, Sept. 24, about five days after an exploit-related halt. Its technical account, @CodeMultiversX, said a recovery upgrade had been deployed, block production had resumed and normal network activity could continue. The official gateway returned a Sept. 24 block timestamp after that all-clear, showing that the network was reporting new blocks.

Kraken's latest posted EGLD notice told a different story for customers of that exchange. Its incident page still showed cancel-only trading and paused deposits and withdrawals when checked Sept. 24, with no resolution notice. Cancel-only lets customers cancel existing orders; it bars new orders and trade execution. The chain's restart therefore did not, by itself, restore the ability to trade EGLD or move it through Kraken.

MultiversX restart in stages

@MultiversX said on Sept. 19 that an attempted exploit of a virtual-machine atomicity issue had caused invalid state changes and prompted a pause in network progression. The Sept. 24 technical update said engineering had completed recovery checks. The two dates put the disruption at about five days, although the statements do not fix the exact stop and restart times.

The MultiversX gateway's post-all-clear timestamp is consistent with the network's report that block production resumed. It cannot show whether a particular customer transaction succeeded or whether a trading venue has reopened its own systems. @CodeMultiversX warned that trading, deposits and withdrawals might remain paused at some exchanges for several more days while those platforms completed their reopening processes. Its all-clear applied to the network, while exchange access required separate confirmation.

That distinction matters for someone deciding which service is available now. The network statement addresses whether on-chain activity can resume; Kraken's notice governs the orders and funding routes handled by Kraken. A new block does not lift an exchange trading restriction or establish that an exchange is accepting deposits. @CodeMultiversX specifically directed users to check their exchange's official updates before using those services. No reopening time appeared on Kraken's incident page at the Sept. 24 check.

Kraken's incident timeline also predates the network halt. The exchange first reported possible EGLD funding-gateway delays on Sept. 16. On Sept. 19 it moved EGLD pairs to cancel-only trading and said deposits and withdrawals remained paused. The initial gateway warning came before MultiversX's exploit announcement, so the dates alone cannot establish a cause for Kraken's original issue or its later escalation.

For EGLD users, the remaining signal is a Kraken update confirming when its trading and funding functions have reopened. Until then, MultiversX's all-clear establishes a path back to on-chain activity, but Kraken's latest posted restrictions still govern what its own customers can do there.