Protocol upgrade decouples consensus from execution
A MultiversX protocol upgrade decouples consensus from execution, letting network nodes agree on blocks before transaction processing completes. The Supernova change, now on testnet, targets scaling bottlenecks by moving execution off the consensus-critical path. Mainnet activation is expected on Sept. 10, 2026, after 600-millisecond blocks since Aug. 20.
Key Takeaways
- MultiversX Supernova, a CTDG Dev Hub participant upgrade, separates block agreement from transaction execution.
- Validators can vote on proposals without re-executing transactions first; execution trails by about one block (~600 ms).
- A virtual mempool, an Execution-Result Inclusion Estimator, and automatic backpressure support the async pipeline.
- Testnet and devnet have produced 600-millisecond blocks since Aug. 20, 2026; mainnet is expected Sept. 10, 2026.
- In-shard finality is typically about 100-250 milliseconds once proofs are available.
What did the protocol upgrade change?
High-performance chains often keep execution inside the consensus path. Validators must execute a block's transactions to confirm state transitions before they can safely agree, so the slowest computation can throttle the whole network.
According to Cointelegraph's DevHub report, MultiversX's Supernova flips that order. The proposer selects transactions and proposes a block without executing them first. Validators check protocol rules and can vote immediately while execution continues asynchronously.
Execution output is normally referenced and notarized in the next block header, so execution trails consensus by roughly one block.
How does Supernova keep pending transactions valid?
Decoupling creates a validity timing gap: the network still needs confidence that proposed transactions will remain valid once execution catches up. Supernova uses a virtual mempool state that looks past the latest executed chain state.
That mempool tracks pending nonces, expected balance consumption, and transactions already proposed but not yet finalized through consensus. Proposers get a forward-looking view of account activity and can select transactions more likely to succeed when their turn arrives.
Two safeguards back the pipeline. The Execution-Result Inclusion Estimator (EIE) caps how many execution results a block can reference based on what minimum-spec nodes can process. Automatic backpressure reduces block capacity if execution falls too far behind.
Why does this matter for builders and users?
For applications that need tight feedback loops—high-frequency DeFi, onchain order books, and similar systems—latency is not a minor annoyance. In-shard finality can land within the same round, often around 100-250 milliseconds, alongside more predictable execution conditions.
Cointelegraph joined MultiversX as a validator through the CTDG program in March 2026. MultiversX is also an official CTDG Dev Hub partner; the MultiversX Foundation has delegated to the CTDG validator, and the Dev Hub team built a dedicated validator dashboard on the network.
Readers following Fintech & Crypto Alerts will watch whether Sept. 10 mainnet delivery matches the live testnet's 600-millisecond block cadence and whether async execution holds under real DeFi load.