MultiversX resumes after an exploit-related halt, but Kraken still blocks new trades in its native token.

MultiversX Restores Mainnet on September 24 After Five-Day Halt, but Kraken Still Limits EGLD Trading

The blockchain network MultiversX said its mainnet returned to service on Thursday, Sept. 24, roughly five days after an exploit-related stoppage. The network's technical account, @CodeMultiversX, reported that a recovery upgrade had been deployed, block production had resumed, and normal network activity could continue. An official gateway displayed a Sept. 24 block timestamp after that all-clear, indicating that the chain was once again reporting new blocks.

For EGLD users using Kraken, however, the restart did not immediately restore full access. Kraken's latest EGLD incident notice, when checked on Sept. 24, still showed cancel-only trading and paused deposits and withdrawals, with no resolution update. That means customers could cancel existing orders but could not place new orders or execute trades on the platform.

A chain restart and an exchange reopening are separate events

The MultiversX update speaks to the state of the underlying network. It confirms that the chain can process new blocks again and that on-chain activity may resume. It does not confirm whether any individual customer transaction succeeded, nor does it show that a centralized service has finished its own internal checks.

Kraken's notice governs a different layer: the trading interface, order matching, and funding routes operated by the exchange. A new block timestamp cannot lift a cancel-only restriction or prove that Kraken has accepted EGLD deposits again. @CodeMultiversX warned that trading, deposits, and withdrawals could remain paused at some exchanges for several more days while those platforms completed their reopening processes. The network all-clear applied to the chain; exchange access required separate confirmation.

This distinction matters most for users deciding what they can do right now. The network statement addresses whether on-chain activity can resume. Kraken's notice addresses what its own customers can do through its platform. The exchange account did not publish a reopening time at the Sept. 24 check.

The path to the Sept. 24 restart

MultiversX first described the disruption on Sept. 19. In that statement, @MultiversX said an attempted exploit involving 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 place the disruption at about five days, although the statements do not specify exact stop and restart times.

The official gateway timestamp after the all-clear is consistent with the network's report that block production resumed. It is not, by itself, proof that every affected service has returned to normal. For users, the more reliable confirmation for any particular platform remains that platform's own status page or official account.

Kraken's EGLD incident began before the chain halt

Kraken's own incident timeline also predates MultiversX's exploit announcement. The exchange first reported possible EGLD funding-gateway delays on Sept. 16. On Sept. 19, it moved EGLD trading pairs to cancel-only mode and said deposits and withdrawals remained paused.

Because the initial gateway warning appeared before MultiversX's exploit notice, the sequence of dates alone cannot establish why Kraken first experienced funding-gateway delays or why the issue later escalated. The available facts show only that Kraken had already restricted EGLD movements before the network halt was announced.

What users should watch next

The remaining signal for EGLD users is a Kraken update confirming that trading and funding functions have reopened. Until that update appears, the MultiversX all-clear establishes a path back to on-chain activity, while Kraken's latest restrictions still govern what customers can do on that exchange. @CodeMultiversX specifically directed users to check their exchange's official updates before using those services.

The immediate practical point is that the network has resumed, but user access may still depend on whether the chosen trading venue has completed its own recovery.