Network upgrades
Protocol and consensus12.4.15+

Network upgrades

Every network upgrade the node knows, with its activation time on mainnet and testnet, what it changed, and how to query the schedule.

Lotus changes its consensus rules at fixed times, about twice a year. Each upgrade has a name and an activation time that is compiled into the node. This page lists all of them and shows how to ask a node which ones are active.

How an upgrade activates #

An upgrade is a Unix time. A block is validated under the upgrade when the median time past (MTP) of its parent block is greater than or equal to that time. The MTP is the median of the timestamps of the last 11 blocks, so it runs behind the clock: an upgrade usually switches on a little after its nominal time, at the same block for every node.

There is no signalling and no vote in the block header. A node that does not know an upgrade keeps the old rules and stops following the chain when the rules differ.

Mainnet schedule #

Times are UTC. The value in the second column is the MTP threshold from src/chainparams.cpp.

UpgradeActivation time (MTP)UTCWhat changed
Exodus16401023402021-12-21 15:59New miner fund address set. Every address of the set is paid in each block.
Leviticus16558028402022-06-21 09:14New miner fund address set, same payout mode.
Numbers16716592802022-12-21 21:48New miner fund address set. The fund becomes one output per block, paid to one address of the set in turn (block height modulo the number of addresses).
Deuteronomy16873594802023-06-21 14:58New miner fund address set.
Joshua17032156202023-12-22 03:27New miner fund address set.
Judges17189166602024-06-20 20:51New miner fund address set.
Ruth17347728002024-12-21 09:20New miner fund address set.
1st Samuel17504737202025-06-21 02:42New miner fund address set.
2nd Samuel17663293802025-12-21 15:03New miner fund address set. Taproot outputs and SIGHASH_LOTUS signatures are accepted from this upgrade.
1st Kings17820302402026-06-21 08:24The miner fund is one output to a single address.
Napoleon17978862002026-12-21 20:50Merged mining, contract opcodes, stricter coinbase rules, mandatory UTXO commitment, new miner fund address. See below.
1st Chronicles18135870002027-06-21 14:10Replay protection: signatures are hashed with the fork value 0xffdead.

In every upgrade the miner fund is half of the block reward. See Block subsidy.

Napoleon upgrade

Napoleon activates when the median time past reaches 1797886200 (21 December 2026, 20:50 UTC). It is a hard fork. From that block:

  • blocks may carry a merged-mining proof from a SHA-256d or Scrypt parent chain (see Merged mining);
  • the contract opcodes are enabled in script;
  • the first coinbase output must carry the block height in the stricter form described in Coinbase tag;
  • every block must carry the UTXO commitment;
  • the limit of three OP_RETURN outputs per transaction is lifted;
  • a coinbase may not overwrite an unspent output;
  • the miner fund goes to a new single address.

The difficulty algorithm does not change on mainnet. The step-by-step guide is in Napoleon.

Testnet schedule #

On testnet (-testnet) every upgrade activates 21 days before mainnet.

UpgradeActivation time (MTP)UTC
Exodus16382879402021-11-30 15:59
Leviticus16539884402022-05-31 09:14
Numbers16698448802022-11-30 21:48
Deuteronomy16855450802023-05-31 14:58
Joshua17014012202023-12-01 03:27
Judges17171022602024-05-30 20:51
Ruth17329584002024-11-30 09:20
1st Samuel17486593202025-05-31 02:42
2nd Samuel17645149802025-11-30 15:03
1st Kings17802158402026-05-31 08:24
Napoleon17960718002026-11-30 20:50
1st Chronicles18117726002027-05-31 14:10

One feature has its own time on testnet: merged mining v2 activates at 1797292800 (15 December 2026, 00:00 UTC), not with the testnet Napoleon. The contract opcodes follow Napoleon.

Napoleon testnet #

The Napoleon testnet (-napoleontestnet) is a separate network with its own genesis block. Every upgrade up to and including Napoleon is active from block 1 there. 1st Chronicles keeps the testnet time, 1811772600.

Shell
lotusd -napoleontestnet
lotus-cli -napoleontestnet getblockchaininfo

Query the schedule #

The REST route /api/v1/upgrades returns every upgrade the node knows, oldest first, with the times of the network it runs on. There is no dedicated RPC for the schedule.

Shell
curl -s http://127.0.0.1:10604/api/v1/upgrades

An entry of the upgrades array looks like this:

JSON
{
  "name": "napoleon",
  "label": "Napoleon",
  "activation_time": 1797886200,
  "active": false,
  "active_since_height": null,
  "seconds_until": 3014626,
  "overridden": false,
  "features": ["mmv2", "contracts", "coinbase-height", "miner-fund"],
  "upstream_name": "secondKings",
  "feature_times": {
    "mmv2": { "activation_time": 1797886200, "active": false },
    "contracts": { "activation_time": 1797886200, "active": false }
  }
}
FieldMeaning
name, labelIdentifier (exodus ... napoleon, firstChronicles) and display name.
activation_timeMTP threshold on this network.
activetrue when the next block is validated under the upgrade (tip MTP is at or past the time).
active_since_heightFirst block validated under the upgrade, or null.
seconds_untilactivation_time minus the tip MTP, 0 once active.
overriddentrue when a start-up option changed the time on this node.
featuresShort tags of what the upgrade switches on.
feature_timesNapoleon only: the own time of merged mining v2 and of the contract opcodes, which test networks can move.

The top level also gives chain, tip_height, tip_mtp, initial_block_download, node_version, client_version, and next, the name of the first upgrade that is not active yet (or null).

The state of replay protection alone is in the replay_protection object of /api/v1/chain; what it means for signers is in Replay protection.

In the dashboard #

The page Network > Upgrades shows the countdown to the next upgrade, what it changes, and whether this node and its peers are ready.

Source share/www/docs/activations.md in the lotusd repository
Checked against src/chainparams.cpp src/consensus/activation.cpp src/minerfund.cpp src/validation.cpp src/api/upgrades_handler.cpp doc/testnet-napoleon.md