| Supernova for builders Dark

Supernova for builders

Mainnet activation: 10 September 2026. The exact time comes with the release announcement on 1 September.

Schedule

Devnet activation, D2.0.4.0

The clock changes at the round, not at the epoch, and the gateway will tell you otherwise. network/config returned erd_round_duration 600 from the epoch boundary at 14:26:20, twenty minutes before block production actually changed at 14:46:20. For those twenty minutes the config declared the new clock while the chain was still producing 6 second blocks. Gate on the round, or measure the interval between consecutive blocks. The declared duration is a promise; the round is the event.

Epoch arithmetic

Mainnet activation epoch is 2233. Missed rounds push the boundary later by minutes. The epoch stays 24 hours, matching testnet and devnet, which both kept their length across the change. The activation epoch itself runs about 20 minutes long. It opens on the old clock, so the rounds before the activation round still take 6 seconds each, and the epoch absorbs the difference. Every epoch after it is 24 hours.

What changes

Why the seconds API is safe

GetBlockTimestamp and GetBlockTimestampMs are separate, separately metered VM hooks. The node divides on the way to the seconds accessor, so a contract that did not ask for milliseconds does not get them.

Breaks after activation

if new_ts > last_ts { /* assumes one block, one second */ }
elapsed_secs = now_secs - start_secs      // 1s resolution on a 600ms chain

Types, mx-sdk-rs

Timestamps and durations do not mix, so unit errors fail the build rather than the contract.

Test on testnet

curl -s "https://testnet-api.multiversx.com/blocks?size=10&shard=1&fields=nonce,timestamp"

Ten blocks span about five seconds, against about a minute on mainnet. Adjacent blocks can carry the same second.

Resources

Questions

Name the integration you want checked before September and we will put the right engineer on it.