MULTIVERSX POST-QUANTUM SECURITY FOUNDATIONS ARE HERE We’ve put together an interactive experience exploring the significance of these milestones, the critical security advances underway, and what they mean for the future of MultiversX.

MULTIVERSX UNLOCKS POST-QUANTUM SECURITY FOUNDATIONS So what does going quantum-proof actually mean, and why does it matter? Here's a brief conversation that makes a complex subject surprisingly accessible.

More to build. Mainnet v2.1.7.0 brings further VM hardening, including improved handling of smart-contract code updates.

The MultiversX–Ethereum bridge has reopened. We’re working closely with exchange partners to restore EGLD deposits and withdrawals as quickly as possible. Each exchange is completing its own checks and will confirm when these services are available.

After carefully reviewing yesterday’s logs, our engineering team confirmed that the recovery hard fork completed successfully. It does not need to be repeated. Validators are now upgrading and synchronizing for the coordinated restart. Please continue to wait for the separate all-clear before submitting transactions. Thank you to our validators, partners and everyone standing with us through these difficult days. We keep building, together.

MultiversX is back online. Thank you for your patience and belief through these hard days. To our validators and partners: thank you for the work that brought us here. We’re proud to be here with you. We continue to build different. Together.

Recovery work continues. The next steps and revised timeline are outlined below. Thank you to the engineers, validators and partners putting in the hours, and to our community for your patience and continued support. We remain focused on bringing MultiversX back online safely.

Tested on Testnet. Rehearsed on Devnet. Now rolling out on Mainnet. Thank you to the engineers, validators and partners working together to bring MultiversX back online safely.

A different kind of weekly update 🌍 On Sep 19, an attempt to exploit a VM-level issue caused invalid state changes, and network progression was paused to protect users. What happened: 🔍 An actor exploited a VM-level atomicity issue; a fix was prepared the same day 🧩 The root cause: an order-of-operations mistake in edge cases, contained fast thanks to the validators' rapid response Where things stand: 🛡 The incident is contained; the attacker's accounts have been identified and frozen with major exchanges, and law enforcement is engaged 🔧 Recovery will be a coordinated hard fork from a known-good checkpoint, rehearsed on Testnet and Devnet with validators first ⚙️ The code is ready and public, and testing is ongoing ⏸️ Until the all-clear: don't submit or rebroadcast transactions, and don't use EGLD/ESDT deposit and withdrawal routes on exchanges or bridges. Exchanges and bridges will reopen in stages after the restart. A full technical incident report will follow. Thank you to the validators, partners and everyone who stood with the network this week. Our regular recap returns once the network is back, with two weeks of building to catch up on.

We are investigating a potential issue detected on the MultiversX mainnet. Our highest priority remains protecting users and ensuring the safe and reliable progression of the network. We will share a further update within the next 12 hours, or as soon a clear conclusion on the matter arises.