MultiversX Foundation

Update: Mainnet is back online. All-clear for normal network activity. The recovery upgrade has been deployed successfully, block production has resumed, and engineering has completed the recovery checks. You can resume using the network. Exchange availability may differ. Trading, deposits and withdrawals may remain paused at some exchanges for a few more days while they complete their own reopening processes. Please check your exchange’s official updates before using these services. We will continue monitoring the network and coordinating with our partners. A full technical incident report will explain what happened, how the recovery was carried out and the measures taken to address the issue. We know this disruption and the wait have been difficult. Thank you to our community for your patience, your support and your belief in what we’re building together. To the engineers, validators and partners who worked side by side to bring the network back online: thank you for your dedication. We move forward together. We continue to build.

Update: The Devnet recovery rehearsal has completed successfully. Following successful recovery runs on both Testnet and Devnet, we are proceeding with Mainnet recovery today, Wednesday, September 23. The planned validator upgrade and synchronization window is 14:00–16:30 UTC today. This preparation period allows participating nodes to become ready before block production resumes. We currently estimate that Mainnet will begin producing blocks at approximately 16:35 UTC, subject to successful completion of the recovery process and validator readiness. This remains an estimate, not a confirmed restart time. Mainnet remains paused, and a separate all-clear will be issued for users. Until then, please do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges. We appreciate your patience as we work to restore Mainnet safely. Thank you to the validators, exchanges and infrastructure partners working with us on the recovery.

Update: The recovery hard fork has been completed successfully on public Testnet. The Devnet rehearsal with validators is now planned for tomorrow, Wednesday, September 23, at approximately 08:00 UTC. Participating validators should prepare to be available from that time. The start and operational instructions will be confirmed in the validator channels. Subject to a successful rehearsal, final checks and coordination with exchanges and infrastructure partners, we are asking validators to prepare to be available from 14:00 UTC tomorrow for Mainnet recovery. This is a tentative coordination time, not the time block production will resume. The restart will follow once validators have synchronized and readiness has been confirmed. Mainnet remains paused. Please continue to wait for the all-clear: do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges. We know the continued wait and changes in timing have been difficult. We deeply appreciate your patience, and thank all the validators and partners supporting the recovery.

📣 MAINNET Upgrade v2.0.9.0 We are upgrading the MAINNET! Version v2.0.9.0 is out. ℹ️ This release fixes the bug that prevented rewards from being claimed. 📅 Activation flag for FixEpochChangeProposedCurrentEpochEnableEpoch is set to 2238, which should happen on Tuesday, September 15th, at 18:05 UTC. Upgrade instructions 👇

Additional Information In plain terms Staking rewards are calculated every epoch and stored so they can be claimed later. During the first epoch transition following Supernova, the system filed the newly calculated rewards under the previous epoch instead of the new one. This created two related problems. First, one day's reward record could replace a reward record already stored in the same position. Second, if someone submitted a claim during this period, the system could move their claim checkpoint forward even when the claim paid 0 EGLD. Repeating the claim moves that checkpoint further and makes the account's recovery history more complex. This is an accounting and record-assignment issue. The underlying EGLD has not left the staking system. We can identify the affected reward periods and restore the amounts through the recovery update. Technical detail Supernova introduced Header V3 behavior for the epoch-change proposal block. That block still carries the number of the epoch being completed, while epoch-start processing needs to operate on the epoch being entered. The staking reward path used the epoch exposed by the block header when selecting the storage key. It therefore wrote the rewards under the previous epoch instead of using the effective epoch for the transition. At the activation boundary, rewards earned during epoch 2232 had already been stored under the epoch 2233 key by the previous flow. The first Supernova transition then stored epoch 2233 rewards under that same key, overwriting the earlier entry. The claim path also used the misaligned epoch value when advancing its checkpoint. A claim could therefore return zero while still moving the checkpoint past a reward period. Different claim histories produce different recovery cases, which is why users should not continue trying to claim. The forward fix will align reward storage and claim checkpoints with the effective epoch used during epoch-start processing. The recovery update will then address the two resulting states separately: Reward entries overwritten at the activation boundary Claim checkpoints advanced without the corresponding reward payment As an immediate mitigation, staking actions have been blocked in the main user interfaces and are being restricted at the gateway level, including relayed transaction paths. This limits the number of affected records while the coordinated fix is prepared and deployed. We will provide further updates as deployment and recovery milestones are completed.

Update on Staking Rewards User advisory Following the Supernova upgrade, we identified an issue affecting the recording and claiming of staking rewards. No funds have been lost or will be lost. Staked EGLD remains secure, and affected rewards will be restored. Until we confirm that the fix is live, please do not perform any staking operation, including: - Claiming rewards - Redelegating rewards - Delegating - Undelegating or unstaking - Withdrawing previously unstaked EGLD If you have already claimed and received 0 EGLD, no action is required. Please do not submit another claim. Each claim can advance an account's reward checkpoint, making the subsequent recovery more complex. We have temporarily disabled staking operations through xPortal and the MultiversX Wallet. The same restrictions are being applied at the public gateway to limit further affected transactions. Fix schedule The immediate fix requires a coordinated network update involving exchanges and other infrastructure partners. The earliest safe deployment window is Monday, Sep 14, 2026. The recovery will happen in two steps: 1. Forward fix: Correct the epoch accounting so that new rewards are recorded and claimed normally. 2. Recovery fix: Restore rewards affected by overwritten records or claim checkpoints that advanced without payment. Staking operations will remain paused until the forward fix has been deployed and verified. We will announce when they can safely resume, followed by confirmation when the recovery has been completed.

📣 MAINNET Upgrade v2.0.8.0 We are upgrading the MAINNET! Version v2.0.8.0 is out. ℹ️ This release brings additional hardening. 📅 No new activation flags. The activation epoch for Supernova is unchanged at 2233, today at ~17:45 UTC. Upgrade instructions 👇