Network upgrade, winter 2026
Napoleon
On 21 December 2026 at 20:50 UTC the Lotus network switches on new consensus rules: Bitcoin and Litecoin miners can mine Lotus, every block commits to the full set of coins, and contracts open. Every node must run lotusd 12.4.13 or later before then.
Napoleon is the upgrade earlier announced as Second Kings: same activation time, new name.

Counting down to 21 December 2026, 20:50 UTC.
- Activation
- 21 Dec 2026
- 20:50 UTC
- Chain median time now
- —
- read from our nodes
- Our nodes run
- —
- lotusd, mainnet swarm
- Block height
- —
- Lotus mainnet
What you need to do
Upgrade to lotusd 12.4.13 or later before 21 December 2026, 20:50 UTC. We recommend 12.4.16, the version all our mainnet nodes run.
A node on an older version, or on another lotusd distribution (versions 11.5.x and 12.0.x included), does not know the new rules. From the first block that uses one of them it follows a different chain from upgraded nodes. That can happen in the very first blocks after activation: there is no grace period.
- Check the version you run. In a terminal:
lotus-cli getnetworkinfoand readsubversion. In a browser: open your node's dashboard, or/api/v1/nodeon its API port. You need/lotusd:12.4.13or higher. Version 12.4.12 was never published; if you run one of its release candidates, upgrade too. - Get the release. Download the latest release for Linux, macOS or Windows, with its checksums (
SHA256SUMS): the Downloads page lists every file, or go straight to the release on GitHub. With Docker:docker pull ghcr.io/lotusdevorg/lotusd:latest. - Install it and restart the node. Keep your data directory: no reindex is needed. The first start computes a hash of the coin set once, which takes a few minutes on mainnet; the log shows
UTXO hash: computingmeanwhile. - Confirm the node knows Napoleon. The dashboard shows an upgrade banner on every page and a full status under Network, Upgrades. The same answer as data:
/api/v1/upgradeslistsnapoleonwith its activation time and whether it is active. - If you build your own blocks, add the commitment. Miners and pools that assemble their own coinbase from
getblocktemplatemust include the coin-set commitment it returns incoinbasetxn.utxocommitment. Blocks without it are rejected from the first block after activation.
Open the web wallet Keys never leave your browser; back up your 12 words.
Until the activation time a 12.4.13 node validates, relays and mines exactly like the previous release, and can be rolled back to 12.4.11. Versions 12.4.14 to 12.4.16 add thin mode, faster relay and reads, block processing about twice as fast and pool fixes, with no consensus change: every one of them is ready for Napoleon, and 12.4.16 is the one we recommend.

What changes at activation
Every rule below starts at the same instant: when the median time of the last 11 blocks reaches the activation time. Nothing activates earlier and nothing activates by block height. The code behind these rules is already in the node: what it does, with the figures we measured.
| Rule | Before Napoleon | From Napoleon |
|---|---|---|
| Merged mining | Lotus blocks carry their own proof of work only. | A block may instead carry a proof from a Bitcoin (SHA-256d) or Litecoin (Scrypt) block header. One parent header proves exactly one Lotus block. The parent's work is scaled so that one ASIC counts as one GPU: a factor of 181,000 for SHA-256d and 5 for Scrypt. |
| Difficulty | Two-day ASERT adjustment. | Unchanged. |
| Coin-set commitment | Not present. | Every block must carry, in its coinbase, a hash (MuHash) of the complete set of unspent coins as of ten blocks earlier. A block without it, or with a wrong one, is invalid. This lets a new node start from a verified snapshot of the coins instead of replaying the whole history. |
| Contracts | Not available. | New script opcodes: transaction introspection, OP_MUL, OP_MULDIV, Taproot state opcodes and OP_CHECKBLOCKHASHVERIFY. Each is a relaxation: nothing that is valid today becomes invalid. |
| Data outputs | At most 3 OP_RETURN outputs per transaction. | No limit on their number. The size limits per output and per transaction stay. |
| Miner fund | Half of every block reward must be paid to the miner fund address lotus_16PSJQXrnTrUbhnxPpPgf1jd16JFkWk8TdbpALVME. | The same half, to a new address: lotus_16PSJPVHNWEF4t1nSFefhth6HAtqn6oripT4k9iNv. A block whose coinbase does not pay it is invalid. The block template lists the required output in coinbasetxn.minerfund. |
| Signatures and replay protection | Transactions are signed with sighash fork value 0. | Unchanged. Replay protection does not start at Napoleon: see below. |
| Coinbase tag | Five letters or digits. | Letters, digits and _, any length. Our nodes will sign their blocks FRENCH_BTC. |
Next upgrade: replay protection, 21 June 2027
Napoleon does not change how transactions are signed. A transaction signed today is signed the same way after 21 December, and wallets and exchanges have nothing to change in their signing code for this upgrade.
Replay protection is set for the upgrade after Napoleon, First Chronicles: when the chain's median time reaches 1813587000 (21 June 2027, 14:10 UTC), signatures must use sighash fork value 0xffdead instead of 0, and a transaction signed the old way is no longer valid. From 12.4.13 the node's own wallet and signing commands pick the right value by themselves. Software that signs Lotus transactions on its own will need to do the same before that date. A node reports the current state in /api/v1/chain, field replay_protection (right now: —).
Until then, there is no replay protection. From Napoleon, this network and nodes of the givelotus 11.6 line follow different chains, but both accept signatures made the old way, so a payment of coins received before 21 December 2026 can be copied onto the other chain until 21 June 2027. To keep coins apart, spend them together with a coin received after Napoleon.
What holders, node operators, developers and exchanges need to do, including for presigned and time-locked transactions: Replay protection.
Mining and the pool
The FRENCHBTC pool is run by the nodes themselves and pays miners directly in the coinbase of each block; there is no pool wallet. It currently has — miners at —. See the pool live.
The miner fund keeps its share at Napoleon, half of each block reward, but its address changes (see the table above). Nodes on 12.4.13 or later build that output themselves. If you assemble your own coinbase, take the output from coinbasetxn.minerfund in the block template: a block that still pays the old address after activation is rejected.
Two pool rules start later, on 15 January 2027 at 08:00 UTC (median time 1800000000): an exact burn split in which no miner is ever overpaid, and a list of accepted payout script types. They are pool rules, not consensus: blocks stay valid for every node either way.

Questions
I only hold or send Lotus. Do I need to do anything?
I run an exchange or a service that accepts Lotus.
/api/v1/upgrades or getnetworkinfo. A node left on an older version will stop following the upgraded network after activation and would report balances and confirmations from a different chain. Consider pausing deposits and withdrawals around the activation time until you see your node on the same tip as the public explorer. Your signing code does not change at Napoleon; it will at First Chronicles in June 2027 (replay protection, above).I mine with a GPU.
I have Bitcoin or Litecoin ASICs.
I operate a node.
What happens to a node that is not upgraded?
How exact is the activation time?

Sources: the lotusd release notes for 12.4.13 and 12.4.14 and the consensus parameters in the lotusd source (miner fund addresses, activation times). Live figures on this page are read from the public API of the Lotus mainnet nodes at the moment you load it.
