The Napoleon upgrade
Napoleon activates on 21 December 2026 at 20:50:00 UTC by median time past; what it changes and what operators, miners, wallets and developers must do.
Napoleon is the network upgrade of winter 2026. It switches on new consensus rules: Bitcoin and Litecoin miners can mine Lotus, every block commits to the full set of coins, and contract opcodes open.
Activation on mainnet: median time past 1797886200, which is 21 December 2026, 20:50:00 UTC. Every node must run lotusd 12.4.13 or later before then. There is no grace period.
Napoleon is the upgrade announced earlier as Second Kings: the same activation time and the same rules, under a new name since 12.4.13.
When it activates #
The rules do not follow the clock but the chain. A block is under the Napoleon rules when the median time past of its parent (the median of the last 11 block times) is 1797886200 or more. The median runs behind the clock, so the first Napoleon block comes shortly after 20:50 UTC.
Nothing activates by block height, and nothing activates earlier. Until that block, a 12.4.13, 12.4.14 or 12.4.15 node validates, relays and mines exactly like 12.4.11.
Your node tells you what it knows:
curl -s http://127.0.0.1:10604/api/v1/upgradesconst r = await fetch('http://127.0.0.1:10604/api/v1/upgrades');
const { upgrades, tip_mtp } = await r.json();
const nap = upgrades.find(u => u.name === 'napoleon');
console.log(nap.active, nap.activation_time - tip_mtp);{
"name": "napoleon",
"label": "Napoleon",
"activation_time": 1797886200,
"active": false,
"active_since_height": null,
"seconds_until": 3014902,
"features": ["mmv2", "contracts", "coinbase-height", "miner-fund"]
}tip_mtp in the same answer is the chain's current median time past. The dashboard shows the same under Network, Upgrades and in a banner on every page.
What changes at activation #
| Rule | Before | From Napoleon |
|---|---|---|
| Merged mining | A block carries its own proof of work | A block may instead carry one parent proof: a Litecoin (Scrypt) or Bitcoin (SHA-256d) header. The parent must meet the Lotus target divided by 5 (Scrypt) or 181,000 (SHA-256d). One parent header proves exactly one Lotus block |
| Difficulty | 2-day ASERT | Unchanged on mainnet |
| UTXO commitment | Not present | Every coinbase must carry the MuHash of the coin set as of 10 blocks earlier. A block without it, or with a wrong one, is invalid |
| Contract opcodes | Fail | Introspection opcodes, OP_MUL, OP_MULDIV, the Taproot state opcodes, OP_CHECKBLOCKHASHVERIFY. Every rule is a relaxation: nothing valid before becomes invalid |
| OP_RETURN outputs | At most 3 per transaction | No limit on their number. The size limits per output and per transaction stay |
| Miner fund | Half of the reward to lotus_16PSJQXrnTrUbhnxPpPgf1jd16JFkWk8TdbpALVME | Half of the reward to lotus_16PSJPVHNWEF4t1nSFefhth6HAtqn6oripT4k9iNv |
| Coinbase tag | 5 letters or digits | Letters, digits and _, any length of at least 1 |
| Signatures | Sighash fork value 0 | Unchanged |
Replay protection is not part of Napoleon. It is set for the following upgrade, First Chronicles, at median time past 1813587000 (21 June 2027, 14:10:00 UTC). /api/v1/chain reports its state in replay_protection. See Replay protection.
The details are in Merged mining, the UTXO commitment and the coinbase tag documents, and Activations.
Node operators #
- Check your version:
lotus-cli getnetworkinfo, fieldsubversion. You need/lotusd:12.4.13or higher. Version 12.4.12 was never published; a 12.4.12 release candidate must be upgraded too. - Upgrade and restart. The data directory is kept.
- Confirm that
/api/v1/upgradeslistsnapoleonwithactivation_time1797886200.
A node on an older version keeps running, but it rejects the first block that uses a new rule and every block after it. From then on it follows a different chain.
Exchanges and services: upgrade every node you rely on. Your signing code does not change at Napoleon.
Miners and pools #
On a pool run by upgraded nodes there is nothing to change: the nodes build the blocks.
If you build your own coinbase from getblocktemplate, take three things from the template:
coinbasetxn.utxocommitment: the UTXO commitment, as a readyscriptPubKey. A block without it is rejected from the first block after activation.coinbasetxn.minerfund: the required miner fund output. A block that still pays the old address is rejected.coinbasetxn.coinbasetag: the coinbase tag output.
ASIC owners: before the activation no Lotus block can come from an ASIC. From the activation the same machines can mine Lotus alongside their parent chain: see Merged mining.
Two pool rules start later, at median time past 1800000000 (15 January 2027, 08:00 UTC): an exact burn split and a list of accepted payout script types. They are pool rules, not consensus; every node of a pool must run 12.4.13 or later before that date.
Wallets and holders #
Coins, addresses and keys do not change. No payment that is valid today becomes invalid. A wallet that talks to a node needs that node to be upgraded. The browser wallet served by an upgraded node needs nothing.
Developers #
- Transactions with more than 3 OP_RETURN outputs relay and confirm from the activation; before it they are refused with
multi-op-return. - Indexers must read every output: several protocol outputs can sit in one transaction.
- Contract opcodes can be tested before the activation on the test networks below.
- Read the commitment with the RPC
getutxocommitmentorGET /api/v1/chain/utxo-commitment/{height}.
Testnets #
| Network | Flag | Napoleon active |
|---|---|---|
| Testnet | -testnet | 21 days before mainnet: median time past 1796071800 (30 November 2026, 20:50:00 UTC). Merged mining v2 follows on 15 December 2026, 00:00:00 UTC |
| Napoleon testnet | -napoleontestnet | From block 1, with merged mining and the contract opcodes |
| Regtest | -regtest | The mainnet time; -napoleonactivationtime overrides it |
To join the Napoleon testnet:
lotusd -napoleontestnet -addnode=51.91.36.126:20605Its ports are the mainnet ports plus 10000, its data goes to napoleontest/ in the data directory and its addresses start with lotusT. It refuses the activation-time overrides: its rules are fixed in the code.
The upgrade guide on the website has a live countdown: lotusia.network/napoleon.
