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.