High-performance blockchains often run into the same architectural limit, where the execution sits directly in the path of consensus. In a conventional synchronous model, validators must first execute the transactions inside that block to confirm the resulting state transitions are valid.
The design keeps the network deterministic, but it also turns computation into a shared bottleneck. Whether they involve richer smart contract logic, cross-system coordination, or heavier state updates, the more complex the transactions are, the more the network’s speed depends on how quickly validators can process them.
The slowest computation on that path can end up constraining the pace of the entire system. Many networks have already spent years improving finality, networking efficiency and block propagation.
Execution has become the next architectural constraint. Rather than only optimizing how quickly validators reach agreement, newer designs are starting to ask whether execution needs to remain inside the consensus loop at all.
Shifting to an asynchronous computation pipeline
CTDG Dev Hub participant MultiversX removes that constraint with Supernova, now live on testnet, by decoupling consensus from execution so the network can agree on blocks before processing their transactions.
Before Supernova, block production followed a sequential pattern. A proposer selected transactions, executed them locally and proposed a block with those results. Validators then had to re-execute the same transactions before voting, which placed execution squarely on the consensus-critical path.
Supernova changes that order: The proposer selects transactions and proposes the block without executing them first. Validators verify that the proposal follows protocol rules and can vote immediately, while execution continues asynchronously in the background. The resulting execution output is normally referenced and notarized in the next block header, so execution trails consensus by roughly one block, or about 600 milliseconds.
Decoupling execution from consensus creates an immediate validity problem: The network must still determine whether a proposed transaction is likely to remain valid before execution catches up. Supernova addresses that with a virtual mempool state.
The mempool looks beyond the latest executed chain state and tracks pending nonces, expected balance consumption and transactions that have already been proposed but whose execution results have not yet passed consensus. Proposers get a forward-looking view of account activity and can select transactions that should still execute successfully once their turn arrives.
MultiversX also adds two safeguards around the new pipeline. The Execution-Result Inclusion Estimator, or EIE, caps how many execution results can be referenced in a block based on what minimum-spec nodes can safely process. Meanwhile, automatic backpressure reduces block capacity if execution falls too far behind, giving the system time to catch up.
Collaborative growth within the decentralized ecosystem
The upgrade also fits into Cointelegraph Decentralization Guardians’ broader work with MultiversX. Cointelegraph joined the network as a validator through the CTDG program in March 2026, extending the relationship into infrastructure participation.
MultiversX is also an official CTDG Dev Hub partner, connecting the protocol to a broader community of developers and blockchain users. The relationship already has practical depth as the MultiversX Foundation delegated to the CTDG validator, and the Dev Hub team built a dedicated validator dashboard on MultiversX.
From a builder perspective, in-shard finality lands as soon as the proof is available, usually within the same round at around 100–250 milliseconds, alongside more predictable execution conditions. These conditions matter most for applications that depend on tight feedback loops, such as high-frequency DeFi primitives, onchain order books and other systems that begin to break down when latency enters the user experience.
Supernova has already been producing 600-millisecond blocks on the live testnet and devnet since Aug. 20, with the broader goal of making onchain interactions feel immediate. Mainnet activation is expected to follow on Sept. 10, 2026. The transition reflects a wider push toward blockchains that behave more like responsive application infrastructure than delayed settlement engines.
