Update: Mainnet remains paused while the coordinated recovery is prepared and tested. We have prepared the protocol correction and is now packaging it into the recovery release. Recovery will be performed through a coordinated hard fork, restarting the network from a known-good checkpoint preceding the incident-related invalid state changes. Earlier today, the recovery plan was reviewed with validators. Their operational feedback is being incorporated into the final procedure. The next steps are to: • finalize the recovery release, checkpoint data and verification material; • rehearse the complete procedure on Testnet and then with validators on Devnet; • provide validators with the official release and a single coordinated restart procedure; • confirm validator, exchange and infrastructure readiness before resuming Mainnet. Mainnet recovery will proceed only after the rehearsals pass and the required readiness is confirmed. Records from the incident-affected interval are being preserved for audit, transaction classification and reconciliation. The resumption of block production will not automatically mean that every exchange, bridge or protocol is ready to reopen. These services will resume separately and in stages after completing their own verification and reconciliation. No action is required from users at this stage beyond waiting for the all-clear. Please do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges. We will communicate again when the recovery package has passed validation and the coordinated Mainnet restart is ready. A full technical incident report will follow once recovery and reconciliation are complete.

Weekly Development Report as of Sep 13, 2026 #multiversxtech 👇⚒️