MultiversX Supernova on September 10: The Hard Fork Checklist for EGLD Holders

On September 10, 2026, the MultiversX network switches over to the Supernova hard fork. For you as an EGLD holder, the most important answer is a reassuring one: if your coins sit in your own wallet, you have nothing to do. There is no token swap, no migration and no claim you would have to register. Addresses, private keys and balances remain backwards compatible according to the project. Anyone who prompts you to take action over the coming days is trying to defraud you. There is still something to be done, and it concerns three places: balances on an exchange, staking, and running a node of your own. The hard fork halts the network for roughly 24 minutes, during which no new transactions are accepted. Anyone needing a withdrawal in that window is better off arranging it beforehand. If you intend to move your coins from the exchange into self-custody anyway, a network upgrade is a good occasion for it; which devices come into question is set out in our hardware wallet comparison. This text answers the questions that have not been put in writing anywhere so far: when the fork really takes effect according to the round arithmetic, how far node migration has actually come today, why the staking unbonding period still takes ten days despite a tenfold increase in speed, and how to recognize the fraud pattern that accompanies dates like this one. What exactly happens at MultiversX on September 10, 2026 Supernova is a hard fork. That is a protocol change all nodes in a network have to adopt at the same time, because the new rules are no longer compatible with the old ones. Anyone leaving the old software running computes differently from the majority from the switchover point on and drops out of the shared chain. What Supernova changes is the core of block production. Until now MultiversX produces a block every six seconds. After the switch it is 600 milliseconds, a tenth of that. This becomes possible because the protocol takes transaction execution out of the critical path of consensus: validators vote on a block while execution continues in parallel, instead of waiting for it. For you as a user this means in everyday terms: a transfer within the same shard is final in fractions of a second rather than in several seconds. The figures for the targeted finality within a shard range between 100 and 300 milliseconds depending on the source; for a transaction across shard boundaries the sources give roughly 1.8 to 2.4 seconds against around 18 seconds so far. That range appears this way in the documents and is not smoothed to a single value here.