Why the 24-minute pause
Mainnet will stop accepting new pool transactions for about 240 rounds — roughly 24 minutes — to clear in-flight transactions. New transactions submitted during that window are expected to stay queued until Supernova begins processing them. The pause is a deliberate step to avoid a messy transition, not a sign of trouble.
What Supernova changes
The upgrade restructures MultiversX's consensus pipeline to allow parallel execution, removing transaction execution from the critical path. That's what unlocks the 10x speed boost. Supernova preserves deterministic finality, with intra-shard finality below 250 milliseconds and cross-shard settlement reduced from about 18 seconds to roughly 2.4 seconds. Epoch length stays the same, and backward compatibility for addresses, keys, and balances is maintained.
Node migration status
As of Sept. 1, 95.35% of the 5,171 nodes were still running v1.11.11.0, meaning migration hadn't visibly started. The planned activation point is round 32157661, with a migration window from Sept. 1 to Sept. 10. Old and new binaries can coexist before activation, but after activation, outdated nodes could produce different transaction results and lose synchronization. That's the risk for operators who drag their feet.
EGLD's weekend move
The token crossed $4 over the weekend for the first time since May, reaching about $4.05 before pulling back. The move came as the upgrade date approached, though the network's fundamentals — not the price — are the focus of the transition.
The migration window closes Sept. 10. Nodes that don't upgrade by then risk falling out of sync once Supernova goes live.
That's about 300 words? Let's count. Actually, we need 500-800. Let's expand a bit. Add more detail about the upgrade's purpose, maybe mention the consensus pipeline restructure in more detail, but we have that. We can add a sentence about the significance of the speed boost. But we must stick to facts. We can mention that the upgrade is designed to improve throughput. But we don't have that explicitly. We have "10x speed boost" from the facts. So we can say that. Let's add a bit more about the pause: "The pause is a deliberate step to avoid a messy transition, not a sign of trouble." That's an interpretation, but it's reasonable. But we should be careful not to invent. We can say "The pause is designed to clear in-flight transactions" - that's from facts. We can say "The pause is a deliberate step" - that's an inference, but it's fine as long as we don't attribute to anyone. We can say "The pause is part of the upgrade process" - that's fine. Let's expand the node migration section: mention that the migration window is tight, and that the high percentage of nodes still on old software suggests many operators are waiting until closer to the deadline. That's an inference, but we can say "The high percentage suggests many operators are waiting until closer to the deadline" - that's an interpretation, but it's not a quote. It's okay as long as we don't attribute to a person. We can say "That leaves a lot of work in the final days" - but we need to be careful. Better to stick to facts: "As of Sept. 1, 95.35% of the 5,171 nodes were still running v1.11.11.0, meaning migration hadn't visibly started." That's factual. Then we can say "The migration window runs from Sept. 1 to Sept. 10, leaving nine days for the bulk of nodes to update." That's a calculation, but it's fine. Let's also add a sentence about the significance of the speed boost: "The 10x speed boost is the headline feature, but the upgrade also tightens finality times." That's from facts. Let's write a more complete article. I'll aim for 600 words. Let me write the full content. Title: "MultiversX Supernova Upgrade to Cut Block Times to 600ms" Slug: multiversx-supernova-upgrade-600ms-block-times Content:MultiversX will pause new transactions for roughly 24 minutes on Sept. 10 as part of its Supernova upgrade, a network-wide change that cuts block times from 6 seconds to 600 milliseconds. The upgrade, activating during epoch 2233, requires more than 5,000 nodes to migrate to new software.
Why the 24-minute pause
Mainnet will stop accepting new pool transactions for about 240 rounds — roughly 24 minutes — to clear in-flight transactions. New transactions submitted during that window are expected to stay queued until Supernova begins processing them. The pause is a deliberate step to avoid a messy transition, not a sign of trouble.
What Supernova changes
The upgrade restructures MultiversX's consensus pipeline to allow parallel execution, removing transaction execution from the critical path. That's what unlocks the 10x speed boost. Supernova preserves deterministic finality, with intra-shard finality below 250 milliseconds and cross-shard settlement reduced from about 18 seconds to roughly 2.4 seconds. Epoch length stays the same, and backward compatibility for addresses, keys, and balances is maintained.
The speed boost is the headline feature, but the upgrade also tightens finality times. Cross-shard settlement dropping from 18 seconds to 2.4 seconds is a significant improvement for applications that rely on quick confirmation across shards.
Node migration status
As of Sept. 1, 95.35% of the 5,171 nodes were still running v1.11.11.0, meaning migration hadn't visibly started. The planned activation point is round 32157661, with a migration window from Sept. 1 to Sept. 10. That leaves nine days for the bulk of nodes to update.
Old and new binaries can coexist before activation, but after activation, outdated nodes could produce different transaction results and lose synchronization. That's the risk for operators who drag their feet. The network needs more than 5,000 nodes to migrate to process the new rules, so the clock is ticking.
EGLD's weekend move
The token crossed $4 over the weekend for the first time since May, reaching about $4.05 before pulling back. The move came as the upgrade date approached, though the network's fundamentals — not the price — are the focus of the transition.
The migration window closes Sept. 10. Nodes that don't upgrade by then risk falling out of sync once Supernova goes live.
That's about 350 words. Need to expand. Let's add more detail about the pause: "The pause is designed to clear in-flight transactions, ensuring that no transactions are left in a limbo state when the new rules take effect." That's an inference but reasonable. We can also add a sentence about the queued transactions: "New transactions submitted during the pause are expected to remain queued until Supernova begins processing them, so users won't lose their transactions — they'll just wait." That's from facts. We can also add a section about the upgrade's purpose: "The upgrade is part of MultiversX's roadmap to scale the network." But we don't have that. We can say "The upgrade is designed to improve throughput" but that's an inference. We have "10x speed boost" so we can say "The upgrade aims to deliver a 10x speed boost" - that's from facts. Let's add a paragraph about the technical details: "The consensus pipeline restructure moves transaction execution off the critical path, meaning the network can process more transactions in parallel. This is a fundamental change to how the network reaches consensus." That's a bit interpretive but based on facts. We can also mention that the upgrade is scheduled to activate on Sept. 10 during epoch 2233. That's in the lead. Let's write a longer version. I'll write:MultiversX will pause new transactions for roughly 24 minutes on Sept. 10 as part of its Supernova upgrade, a network-wide change that cuts block times from 6 seconds to 600 milliseconds. The upgrade, activating during epoch 2233, requires more than 5,000 nodes to migrate to new software.
Why the 24-minute pause
Mainnet will stop accepting new pool transactions for about 240 rounds — roughly 24 minutes — to clear in-flight transactions. New transactions submitted during that window are expected to stay queued until Supernova begins processing them. The pause is a deliberate step to avoid a messy transition, not a sign of trouble. It gives the network a clean slate to switch over to the new consensus rules.
What Supernova changes
The upgrade restructures MultiversX's consensus pipeline to allow parallel execution, removing transaction execution from the critical path. That's what unlocks the 10x speed boost. Supernova preserves deterministic finality, with intra-shard finality below 250 milliseconds and cross-shard settlement reduced from about 18 seconds to roughly 2.4 seconds. Epoch length stays the same, and backward compatibility for addresses, keys, and balances is maintained.
The speed boost is the headline feature, but the upgrade also tightens finality times. Cross-shard settlement dropping from 18 seconds to 2.4 seconds is a significant improvement for applications that rely on quick confirmation across shards. The parallel execution model means the network can handle more transactions per second, though the exact throughput numbers aren't part of the announcement.
Node migration status
As of Sept. 1, 95.35% of the 5,171 nodes were still running v1.11.11.0, meaning migration hadn't visibly started. The planned activation point is round 32157661, with a migration window from Sept. 1 to Sept. 10. That leaves nine days for the bulk of nodes to update.
Old and new binaries can coexist before activation, but after activation, outdated nodes could produce different transaction results and lose synchronization. That's the risk for operators who drag their feet. The network needs more than 5,000 nodes to migrate to process the new rules, so the clock is ticking. The high percentage of nodes still on the old version suggests many operators are waiting until closer to the deadline, but the window is tight.
EGLD's weekend move
The token crossed $4 over the weekend for the first time since May, reaching about $4.05 before pulling back. The move came as the upgrade date approached, though the network's fundamentals — not the price — are the focus of the transition.
The migration window closes Sept. 10. Nodes that don't upgrade by then risk falling out of sync once Supernova goes live.
That's about 450 words. Need a bit more. Let's add a sentence about the pause duration: "The 24-minute pause is short compared to the overall upgrade process, which has been in the works for months." But we don't have that. We can say "The pause is a brief interruption in a network that typically runs continuously." That's an inference. Better to add a sentence about the queued transactions: "Users who submit transactions during the pause shouldn't panic — they'll be processed once Supernova goes live." That's a bit of advice, but it's based on the fact that they
