MultiversX Supernova launches September 10: Hard Forking Operation Guide for EGLD Holders

September 10, 2026 MultiversX Network Upgrade to Supernova Hard Fork: A Holder's Guide

On September 10, 2026, MultiversX Network will switch to Supernova Hard Fork. For EGLD holders, the most important answer is reassuring: If your tokens are stored in your wallet, you don't need to do anything. There are no token redemption, no migration steps, and no registration to collect it. According to the project party's instructions, the address, private key and balance are backward compatible. In the next few days, anyone who urges you to take action will try to defraud you.

However, there are still some matters that need to be dealt with, mainly involving three aspects: exchange balances, pledges and running your own nodes. The hard fork will suspend the network for approximately 24 minutes, during which time no new transactions will be received. If you need to withdraw cash within this window period, it is best to arrange in advance. If you plan to transfer tokens from exchanges to self-custody anyway, this network upgrade is a good opportunity; for specific devices involved, please see our Hardware Wallet Comparison article.

This article answers questions that have not been answered in writing anywhere before: when does the fork actually take effect based on round calculations; what is the actual progress of node migration; why is the pledge unlock period still ten days despite the tenfold increase in speed; and how to identify fraud patterns that accompany such dates.

What happened to MultiversX on September 10?

Supernova is a hard fork. This means that all nodes in the network must adopt protocol changes simultaneously because the new rules are no longer compatible with the old rules. Starting from the switching point, nodes that continue to use old software will compute differently from most nodes, leaving the shared chain.

Supernova has changed the core of block production. As of now, MultiversX generates a block every six seconds. After the switch, this time was shortened to 600 milliseconds, only one-tenth of the original. This is possible because the protocol moves transaction execution off the critical path of consensus: when the verifier votes on a block, the execution process proceeds in parallel rather than waiting for execution to complete.

For users, this means a change in the daily experience: transfers within the same shard can be finally confirmed in a fraction of a second, rather than the seconds before. Data on target finality within a shard is displayed between 100 and 300 milliseconds, depending on different sources; the confirmation time for cross-shard transactions is approximately 1.8 to 2.4 seconds, compared with approximately 18 seconds previously. This range is presented in the document and is not smoothed to a single value here.

Supernova analysis: Why block time dropped from six seconds to 600 milliseconds

Shard is a separate part of the blockchain that processes its own transactions;MultiversX currently operates three shards plus a coordinating meta-chain. This division has always been a bottleneck before: payments from fragment A to fragment B require three rounds, because the meta chain must first authenticate the block of the sender fragment before the recipient fragment is allowed to accept it.

Supernova accelerates both sides of the calculation. Round times have become shorter and the order has changed: the verifier starts executing blocks immediately after passing the local check, and then votes are cast. The final cleanup across shards is still bound to the metachain, so cross-shards payments arrive only when the block partitioned by the sender is proven final.

Achieving this goal is not a short-term decision. According to the project documents, the change was adopted through on-chain voting from January 8 to 18, 2026, and received 99.64% approval under a quorum of 33.63% voting rights participation. The public stress test will be conducted from March 11 to 31, 2026. According to the project party, the network carried 120,000 transactions per second on the last day. The external security audit will be completed in June 2026.

When will a hard fork really switch? Recalculation of activation rounds

switching depends on the "rounds" rather than the clock time. Rounds are the fixed rhythm at which the network is allowed to generate blocks. The main network configuration as of August 31, 2026 specifies the 32,157,661st round of the 2233rd era as the activation point. "Era" is the cycle in which MultiversX reassigns verifiers between shards, which lasts for 24 hours.

We could convert this number to clock time, and we did the query ourselves rather than copying the report directly. The data returned by querying the official main network gateway at 00:36:48 UTC on September 6, 2026 shows that the current round is 32,089,568, the era is 2228, the round duration is 6,000 milliseconds, 14,400 rounds per era, and the current era starts at the 32,085,434 round.

It is inferred from this that there are still 68,093 rounds away from the activation round. Multiply by six seconds, which is 408,558 seconds or 113.5 hours. Therefore, the switch occurred at approximately 18:06 UTC on September 10, 2026, which is around 8:06 pm German time. Using the same calculation, the 2233rd Era begins at round 32,157,434, which is approximately 17:43 UTC; the activation round follows it 227 rounds. The "2233rd Era" statement in the report is consistent with the chain data.

One thing to add: This is round arithmetic, not a commitment. If a block producer misses a round due to not using its slot, the time point moves forward. In fact, this involves differences from minutes to hours. What remains exactly unchanged is "September 10, around 6:00 pm UTC time", not to seconds.

The network will not accept new transactions for approximately 24 minutes. Content submitted during this period will wait in the queue.

EGLD in your own wallet: Why self-custodians don't need to operate

This is the core point for most readers. MultiversX explicitly maintains backward compatibility with addresses, keys, and balances. Your mnemonics are still valid, your address remains the same, and your balance remains where it was. There are no new tokens and there is no need to move anything.

For you, changes will only occur after the fork and notice faster confirmation speeds. Wallet apps connected to the network will automatically adapt to the new rhythm. The hardware wallet continues to sign the same transaction format; it knows nothing about block time.

One duty of care still needs to be fulfilled: Keep the wallet app updated. Applications that derive time windows or fees based on old block times may display erroneous estimates after switching. This is a display error, not a risk of financial loss, but it will cause inconvenience.

No token redemption, no withdrawal: How to identify hard fork scams

Before such network changes, websites and private messages requiring "token migration","snapshots" or "wallet upgrades" often appear. But in Supernova, none of this exists. There was no redemption, no collection, and no registration.

There are three characteristics that allow such quotes to be identified without technical background knowledge. First, a real agreement change never requires a mnemonic; the person asking for the mnemonic wants your money. Second, holders have no deadline, so there is no time pressure. Third, the project communicates through its official channels rather than through proactive private messages contacting you.

This warning does not refer to known events surrounding Supernova. It is noted here because the pattern reappears in every announced fork. For other chain situations, please refer to our reports on the Zilliqa hard fork and the ZIL migration (unlike here, migration did occur there), as well as our analysis of the Mina hard fork and its network suspension.

EGLD on exchanges: Why should you check withdrawal windows in advance

If your coins are stored on a trading platform, you don't have your own key and therefore cannot make your own decisions. During network changes, exchanges usually suspend deposits and withdrawals for a period of time, but transactions continue. This is a routine operation and not a warning signal.

Our self-verification status is that at approximately 00:40 UTC on September 6, 2026, Binance's announcement catalog (including listings, removals and general news) did not contain any notices about EGLD or Supernova. This does not mean that there will be no notification. Experience shows that such notices usually appear one to three days before the date. This means that you cannot rely on known withdrawal windows today.

A simple rule comes from practice: If you plan to extract EGLD in the next few days, please do so before September 10, not the same day. Anyone who wants to take this opportunity to change providers can look up the terms in our crypto exchange comparison article. How tight such deadlines are actually is, we have analyzed in current cryptocurrency deadlines and deadline statistics.

Pledge and commission: The unlock period remains ten days

Pledge means assigning your EGLD to a pledge provider, who can use it to ensure network security and share rewards for you. If you want to recover your funds, you need to start the unlocking process and then have a fixed waiting time before you can move your funds.

This is the biggest misunderstanding surrounding this upgrade. A network that is ten times faster will not make balances released ten times faster.

The unlocking period remains unchanged for a full ten days. We made no assumptions, but looked up this information directly in the network configuration. The configuration currently displays two values side by side: erd_unbond_period is 144,000 rounds and erd_unbond_period_supernova is 1,440,000 rounds. Converting the two into time, the result is the same: 144,000 rounds are 864,000 seconds measured in six seconds, and 1,440,000 rounds are also 864,000 seconds measured in 0.6 seconds. A full ten days in both cases. The number is multiplied by ten because the rounds are shorter; the waiting time behind it remains the same.

For you, this means: Whether or not the fork is sandwiched in the middle, the unlocking initiated today will end at the same time. Unlocks initiated after September 10 take as long as before. If you are reviewing the location of pledges and their benefits, our pledge platform comparison articles will help you filter. Similar problems also occurred when Solana was upgraded, and we have analyzed them in the text on Alpenglow and its impact on pledges.

Ten days is still ten days: the value of the unlock period is multiplied by ten, but the waiting time behind it remains unchanged.

84% instead of 4.6%: Actual progress of node migration

Whether a hard fork works smoothly depends on how many nodes migrate to the new software in a timely manner. As of September 1, 2026, the findings are sobering: Based on assessments from public network data, 95.35% of the 5,171 nodes are still running the old version of v1.11.11.0. Only about a quarter of the migration has been completed.

We repeated this measurement on September 6, 2026 at 00:37 UTC via the public endpoint www.example.com. api.multiversx.com/nodes/versions The situation reversed within five days: 83.02% of nodes were running v2.0.6.0, and another 1.24% were running the reported version of v2.0.6. The total is 84.26%. Another 13.6% are still stuck in the old version of v1.11.11.0. The remaining 2.14% is distributed among older versions of the 1.11 series, as low as v1.11.0.0.

The total number of nodes is 5,176. The absolute number is approximately 4,361 updated nodes and approximately 704 old major version nodes. This number is a true leading indicator for September 10, and anyone can follow up on their own: the endpoint is public and provides share values for each software version. Anyone who wants to know whether the switching is in an orderly manner can check again the day before.

What happens if too few nodes migrate in time?

Prior to activation, old and new versions of the program can coexist without anything happening. The new processing rules will only take effect from the activation round. Nodes with old software may then produce different results for the same transaction and lose connectivity to most chains.

For individual operators, this means downtime and missed rewards. For the network, it becomes difficult only when a large number of shares are left behind, because block production will be spread over fewer shoulders. Given that approximately 84% of nodes are currently updated, there is no indication pointing to this situation.

As an EGLD holder, you do not need to draw any conclusions from it. There are no buttons to press and no choice between two chains. This issue is only relevant for operators and determining whether longer waiting times will occur during the handover window.

Node operators: Mandatory software versions starting from Round 32, 157, 661

If you run the validator or observe the node yourself, fork means work. Version v2.0.5.0 and above is required; chain current report v2.0.6.0 is the current flag. This value is located in the erd_latest_tag_software_version field of the network configuration and is set during a query at 00:36 UTC on September 6.

Prior to the activation round, the migration itself is risk-free because two versions can coexist. After activation, migration is no longer optional. People who miss the date must catch up later and synchronize the nodes again. Verifiers with a minimum pledge of 2,500 EGLD should not let this happen.

Smart contracts and dApps: Why post-Supernova timestamps are no longer unique

This indirectly affects you, but is the most underestimated part of the entire upgrade. Smart contracts are programs that sit on a blockchain to automatically enforce rules, such as deposit interest or preferential terms.

Many such programs calculate timestamps in seconds. As long as a block is created every six seconds, the second-level timestamp can uniquely identify a block. After switching, ten blocks are accommodated in the same second, and the timestamps are no longer unique. The project document publicly points out the consequences and gives examples: the check that "the new time point must be greater than the previous time point" may fail. If measured in seconds, the limit of one operation per block may be bypassed, and the expiration period will be longer than expected. Reward calculations that use time differences as divisor may encounter division by zero.

For users of DeFi apps on MultiversX, this means: Isolated display errors may occur in the days after September 10, or applications may suspend service out of caution. Those affected are application operators that are not prepared for the change. The balance in your own wallet is not affected. If you have a large amount of money deposited in a small provider's app, checking its announcements before the date is the cheapest precaution.

What a hard fork is not: no deadline, no price statement

Three clarifications to avoid false expectations from this date.

This is not the deadline for holders.

Unlike migrations with exchange windows, nothing will expire here. People who did nothing until September 10 would have exactly the same coins after that.

This is not a price statement.

According to CoinGecko data, EGLD was quoted at $4.61 (or 3.97 euros) at 00:34 UTC on September 6, 2026, about 3% lower than the previous day and about 27% higher than the level seven days ago, with a market value of approximately US$141.5 million. These data are only used as a snapshot, not a basis for predictions. Whether technological upgrades will be reflected in prices cannot be seriously determined in advance.

This is not a given fact.

The handover depends on the migration of nodes, and although it is progressing smoothly, it has not yet been completed as of September 6. Dates may be delayed by minutes to hours due to turns rather than clocks.

The timetable before September 10 lists what reasonably happens in the remaining days

, in the order of occurrence:

• to September 9: If you need it in these days, please clear the exchange's withdrawal. Pay close attention to provider announcements, as experience shows that they are usually temporary notices.
• On the morning of September 10: If you are concerned about whether the switching is in an orderly manner, please check the version status of the node again.
• September 10 UTC approximately 17:40 to 18:10: Do not submit time-sensitive transactions. The content you submit will not be lost, but initially it will just wait in line.
• After that: If the app clearly misjudges deadlines or fees, update your wallet app.

MultiversX Supernova: Information you should take with you

Self-hosting does not require action, but requires vigilance.

There were no tokens exchanged and no withdrawals. Any such reminder is a fraud attempt, and the response is consistent: mnemonic words are never provided, nowhere is provided. If you take the opportunity to transfer coins from providers to self-hosting, you can find the relevant device in the Hardware Wallet Comparison article.

Check if your balance can be accessed before September 10.

Exchanges usually temporarily announce a temporary suspension of withdrawals, but there was no notice on September 6. Anyone who wants to replace or withdraw cash should act in advance; see the exchange comparison article for terms.

Continue to calculate the pledge time based on ten days.

Faster chains have not shortened the unlock period, although the numbers in the configuration now seem ten times larger. Your pledge location and income can be sorted out through the pledge comparison article.

(As of September 6, 2026. This article does not constitute investment advice. Price and fee structures are subject to change; please check terms with your provider before purchasing.)

Sources and evidence: Chain data comes from the official network configuration of the MultiversX main network gateway; activation rounds, 24-minute window and version status on September 1 are from CryptoSlate's report on September 2, 2026.