Repository navigation
Lotus Root v12.4.13
The Napoleon network upgrade: required before 21 December 2026
Important
Every node operator, pool and exchange must run 12.4.13 or later before 2026-12-21 20:50 UTC.
A node on an older version, or on any LotusiaStewardship release, leaves the chain at the first block that uses the new rules. There is no grace period.
Miners and pools that build their own coinbase must add the UTXO set commitment before that date.
Warning
Known issue, fixed in 12.4.15: these binaries cannot create or load an SQLite wallet, and a node started with -wallet= on such a wallet does not start. If you use the wallet, install 12.4.15.
- Merged mining. From Napoleon a Lotus block can be mined together with Bitcoin or Litecoin: one parent header proves one Lotus block.
- Contract opcodes. New script opcodes for contracts (introspection,
OP_MUL,OP_MULDIV, Taproot state,OP_CHECKBLOCKHASHVERIFY) activate at Napoleon. - UTXO set commitment. From Napoleon every block commits to the UTXO set in its coinbase, so a snapshot can be checked against the chain.
- UTXO snapshots. A node can start from a UTXO snapshot and validate the history in the background. Full nodes write one every 100 blocks.
- No more limit of 3
OP_RETURNoutputs per transaction, from Napoleon. - Before Napoleon nothing changes: a 12.4.13 node validates, relays and mines exactly like 12.4.11.
New here? The install and upgrade guide takes you from download to a running node.
Downloads
Node and tools
The archive holds lotusd and its tools (lotus-cli, lotus-tx, lotus-wallet, and lotus-seeder where it is built).
| Platform | File | Size |
|---|---|---|
| Linux x86_64 | lotus-binaries-12.4.13-linux-x86_64.tar.gzone program only: lotusd · lotus-cli · lotus-tx · lotus-wallet · lotus-seeder |
30.4 MB |
| Windows x86_64 | lotus-binaries-12.4.13-windows-x86_64.zipone program only: lotusd · lotus-cli · lotus-tx · lotus-wallet |
16.7 MB |
| macOS Intel (x86_64) | lotus-binaries-12.4.13-macos-x86_64.tar.gzone program only: lotusd · lotus-cli · lotus-tx · lotus-wallet · lotus-seeder |
27.0 MB |
GPU miner
| Platform | File | Size |
|---|---|---|
| Linux x86_64, NVIDIA | lotus-gpu-miner-nvidia-12.4.13-linux-x86_64.tar.gz |
2.7 MB |
| Linux x86_64, AMD | lotus-gpu-miner-amd-12.4.13-linux-x86_64.tar.gz |
2.7 MB |
Lotus Miner desktop app
| Platform | File | Size |
|---|---|---|
| Linux x86_64 | lotus-miner-gui-12.4.13-linux-x86_64.tar.gz |
20.8 MB |
| Windows x86_64 | lotus-miner-gui-12.4.13-windows-x86_64.zip |
10.2 MB |
| macOS Intel (x86_64) | lotus-miner-gui-12.4.13-macos-x86_64.zip |
9.7 MB |
| macOS Apple Silicon (arm64) | lotus-miner-gui-12.4.13-macos-arm64.zip |
8.8 MB |
| macOS universal (Intel + Apple Silicon) | lotus-miner-gui-12.4.13-macos-universal.zip |
18.0 MB |
Checksums of every file: SHA256SUMS.
Docker
docker pull ghcr.io/lotusdevorg/lotusd:12.4.13 # the node
docker pull ghcr.io/lotusdevorg/lotus-cli:12.4.13 # command-line client
docker pull ghcr.io/lotusdevorg/lotus-tx:12.4.13 # transaction tool
docker pull ghcr.io/lotusdevorg/lotus-seeder:12.4.13 # DNS seeder
docker pull ghcr.io/lotusdevorg/lotus-wallet:12.4.13 # wallet tool
docker pull ghcr.io/lotusdevorg/lotus-gpu-miner:12.4.13 # GPU miner, NVIDIA
docker pull ghcr.io/lotusdevorg/lotus-gpu-miner-amd:12.4.13 # GPU miner, AMDTo pin the exact node image, pull it by digest:
docker pull ghcr.io/lotusdevorg/lotusd@sha256:f5e8b35f7d6b1016c4e0c7822aea851d95d878df7ea831c5cffc21b3e9afd94eVerify your download
Every file of this release is listed in SHA256SUMS. Download it next to your file and check:
curl -fsSLO https://github.com/LotusDevOrg/lotusd-releases/releases/download/v12.4.13/SHA256SUMS
curl -fsSLO https://github.com/LotusDevOrg/lotusd-releases/releases/download/v12.4.13/lotus-binaries-12.4.13-linux-x86_64.tar.gz
sha256sum -c --ignore-missing SHA256SUMS # Linux; must print: OK
shasum -a 256 -c --ignore-missing SHA256SUMS # macOSOn Windows, Get-FileHash <file> -Algorithm SHA256 in PowerShell must give the value on that file's line. The files are not signed: download them from this page only.
Full release notes
12.4.13 is the release first planned as 12.4.12 (no v12.4.12 tag was
published; the mainnet fleet ran 12.4.12 release candidates before it), plus
the fixes below.
Consensus release. 12.4.13 activates new consensus rules on mainnet at
Napoleon (called Second Kings upstream): median time past of the previous block at or after
1797886200 (2026-12-21 20:50:00 UTC), the same test as every other Napoleon
rule. Until then a 12.4.13 node validates, relays and mines exactly like
12.4.11.
Fixes since the 12.4.12 release candidates
- Pool: a node's own shares are no longer lost when blocks arrive in a
burst (the job cache evicted the tip job by arrival time, so about 10% of
the fleet's own blocks were classed as spoofs); eviction is now by height
and never at or above the tip, a missing job is restored from the stratum
job served, andcounters.localShareDrops,localBlockShareDropsand
localJobsRestoredreport it. The round effort (luck) is computed from
the share heights above the last settled pool block. - Dashboard: the Social overview sits on one 12-column grid with rows of
equal height; the upgrade banner and checklist say operators must run
12.4.13 or later. - Pool: re-hello of unknown peers after a restart (a one-sided
poolhello
is repaired;counters.rehellos); deep catch-up to the block-proof
retention horizon. - REST:
txs/<txid>/rawlooks again on the shared connection before
answering 404 (a transaction indexed in a batch not yet committed during
IBD was reported missing). - HTTP: over-long request and header lines are cut while being read
(400/414), so a client cannot make the server buffer an unbounded line. getblocktemplategives the coinbase tag output
(coinbasetxn.coinbasetag) for external pools that build their own
coinbase.- Startup page and
debug.log: real progress (%) for the one-time UTXO set
hash build on the first start (reporting only; the hash is unchanged). - Dashboard: the ASIC login builder uses the node's network address prefix
and refuses addresses of another network. - Build: MuHash3072 compiles with the macOS toolchain (no semantic change);
the UTXO commitment chain tests now run undercheck.
New in 12.4.13 (non-consensus)
- UTXO snapshots (doc/utxo-snapshot.md): a node can start from a
release-pinned UTXO snapshot (-loadutxosnapshot=<file>, or the
loadtxoutsetRPC) and validates the history in the background
(-snapshotverify, default on; the node stops if the history disagrees).
Snapshots are checked against the Napoleon UTXO commitment where one exists.
Every full node writes a periodic snapshot every 100 blocks (about
3 h 20 min), at the heights that are multiples of 100 (the same on every
node, so all of them serve the same files), each one written 110 blocks
later, once the coinbase commitment to it (block H + 10) is 100 blocks
deep: every snapshot a node lists can be checked against the chain at
once. On mainnet and testnet-utxosnapshotintervalonly turns them off
(0); other values are ignored with a warning. The write runs in the
background from a consistent view (cs_mainonly for a flush); a
snapshot that falls due while the previous one is still being written is
skipped, not queued. Only the latest complete snapshot is kept, plus the
one being written (-utxosnapshotkeep, default 1, at most 4): about
0.3 GB each on mainnet (6.2 M coins), 0.7 GB at most on disk, ~2-2.5 GB
written per day; skipped when disk is short (-utxosnapshotminfree).
Nodes serve them (-utxosnapshotserve);/api/v1/utxo-snapshots
advertises the latest height, the interval, the height being written and
the next one.downloadutxosnapshottakes height 0 for the newest one
and restarts on the new one when the server rotates it out during the
download; a partial file is resumed only for the same snapshot. The
per-block UTXO hash history (-utxohash) follows that setting.
Developers › UTXO snapshots in the dashboard shows them. dumptxoutsetbelow the tip (and the periodic snapshots): the
rollback now restores every input of a block before removing its
outputs. With the canonical transaction order a child can precede its
parent in a block; the former per-transaction pass brought back outputs
created and spent in the same block, so a dump below such a block had a
wrong set (its MuHash disagreed with the hash history, and the periodic
snapshot was deleted by its self-check).- Light full node options (thin mode phase 0, doc/thin-mode.md), all
off by default:-explorerindex=0skips the explorer tables (~90% of a
synced datadir; explorer routes answer 503explorer_disabled) and
-modules=<list>runs only the listed chain modules. Loading a snapshot
needs-explorerindex=0 -modules=none. - Mempool overlay (doc/mempool-overlay.md,
-mempooloverlay, default
on): REST address, UTXO and transaction answers include unconfirmed
transactions, with SLP/ALP token data; push notifications carry token
events. - PWA wallet: never spends an immature coinbase output (fewer than 100
confirmations); the node's refusal maps to "spendable after 100
confirmations". - Releases now include the GPU miner (NVIDIA and AMD) and the miner GUI
(Linux, Windows, macOS), with SHA256SUMS.
Upgrade before 2026-12-21
Every node operator, pool and exchange must run 12.4.13 before Napoleon.
After the activation:
- the first merged-mined block (a Lotus block whose proof of work is a
Bitcoin or Litecoin parent header, carried in block metadata field 1 or 2)
is valid for 12.4.13 and invalid for every other node; - the first transaction that spends with a contract opcode (introspection,
OP_MUL,OP_MULDIV, the Taproot-state opcodes,OP_CHECKBLOCKHASHVERIFY,
or a Taproot leaf above the old 400-op limit but within its cost budget) is
valid for 12.4.13 and invalid for every other node; - the first block with a transaction or a coinbase carrying more than 3
OP_RETURN outputs is valid for 12.4.13 and invalid for every other node. - the first block whose coinbase tag contains
_(our fleet's
FRENCH_BTC) is valid for 12.4.13 and invalid for every other node,
12.4.12 release candidates included. - every block must carry the UTXO set commitment in its coinbase (see
below). From the very first block after the activation, a block without it
is invalid for 12.4.13. Miners and pools who build their own coinbase (from
getblocktemplate) must add it before 2026-12-21, or their blocks are
rejected.
A node that is not on 12.4.13 splits from the chain at the first such block.
That includes nodes on 12.4.11 or older of this fork, and every
LotusiaStewardship/lotusd release (v12.0.0 included): those rules do not exist
upstream. Both events can happen in the very first blocks after the
activation, so there is no grace period.
Nothing activates by height; nothing activates before the time above. Testnet
and regtest follow their own Napoleon times, and accept the
-mmv2activationtime / -contractsactivationtime overrides (refused on
mainnet).
Renamed: Second Kings → Napoleon
Napoleon is the network upgrade called Second Kings upstream and in LotusiaStewardship v12 ("2nd Kings" in its docs and code: IsSecondKingsEnabled, secondKingsActivationTime). We renamed it in 12.4.13; it is the same upgrade, with the same activation (median time past 1797886200 = 2026-12-21 20:50 UTC on mainnet, 2026-11-30 20:50 UTC on testnet) and the same rules.
Nothing else changes: no rule, no date, no behaviour. Old names that keep
working in 12.4.13 (deprecated, removed in 12.4.14):
| Old name (deprecated) | New name | Notes |
|---|---|---|
-secondkingsactivationtime |
-napoleonactivationtime |
same value; if both are set the new one wins; a "deprecated" line is logged at startup |
-coinbasetagaftersecondkings |
-coinbasetagafternapoleon |
same |
getmininginfo → coinbasetag.secondkings |
coinbasetag.napoleon |
both returned |
getmininginfo → coinbasetag.aftersecondkings |
coinbasetag.afternapoleon |
both returned |
Renamed without an alias:
getmininginfo→coinbasetag.reasonvaluespre-second-kings-needs-5-chars
andafter-second-kings-not-enabledare nowpre-napoleon-needs-5-charsand
after-napoleon-not-enabled(one field cannot carry both spellings);- C++:
IsSecondKingsEnabled→IsNapoleonEnabled,
Consensus::Params::secondKingsActivationTime→napoleonActivationTime,
CoinbasePayoutAddresses::secondKings→napoleon; - tests:
mining_pool_second_kings.py→mining_pool_napoleon.py,
p2p_pool_second_kings_fleet.py→p2p_pool_napoleon_fleet.py,
interface_nng_mining_second_kings.py→interface_nng_mining_napoleon.py,
test_framework/sk_pool_util.py→napoleon_pool_util.py; - the contract spec LIP-SK-1 is now LIP-NAP-1 (
doc/contracts/spec.md).
Branches written before the rename: merge it, then run
contrib/devtools/rename-napoleon.sh and --check (see the script's header).
What activates at Napoleon
Merged mining v2 (Bitcoin and Litecoin parents)
- A block may carry, instead of native proof of work, one parent proof:
a Scrypt (Litecoin) parent in metadata field 1 or a SHA-256d (Bitcoin)
parent in field 2, with the positional anchor (fields 3 and 4, at least
8 bytes). The parent header must meet the Lotus target divided by the
multiplier: 5 for Scrypt, 181,000 for SHA-256d (one ASIC counts as
one GPU, owner decision of 2026-11-14). Chain ID 4418. One parent header
proves exactly one Lotus block. - A header whose own hash does not meet its target is never indexed without
its proof: nodes fetch the blocks of such headers before accepting them
(header-first sync with proof windows,doc/asic-merged-mining.md1.7). - Difficulty: unchanged on mainnet. Every block, before and after the
activation, keeps the 2-day ASERT anchored at block 1
(asert_half_life_seconds= 172800); the MMv2 difficulty track (2-hour
half-life) and the Real Time Targeting policy are testnet/regtest only
(fMMv2OwnDAAfalse on mainnet, owner decision of 2026-11-15). - The legacy AuxPoW regime (
auxpowActivationHeight) stays off on mainnet.
Contract opcodes (LIP-NAP-1, doc/contracts/spec.md, frozen)
- Native introspection 0xc0-0xcd (BCH byte values), Taproot state and
commitment opcodes and value sums 0xd4-0xd9,OP_MULDIV0xda,
OP_MULre-enabled. OP_CHECKBLOCKHASHVERIFY(wasOP_NOP4): the hash of a block at least 100
blocks below the spending block.- Taproot leaves: the 400-op limit becomes "fail only if over 400 ops AND
over (41 + scriptSig size) x 800 cost units"; leaf script and control block
pushes up to 10,000 bytes. Every rule is a relaxation: nothing valid before
becomes invalid. - Without the activation the interpreter is byte-identical to 12.4.10/12.4.11
(860,872-run equivalence digest).
No more 3-OP_RETURN cap per transaction
- Every node checks standardness on block transactions
(fRequireStandardConsensus, always on for mainnet), so "at most 3 OP_RETURN
outputs per transaction" (IsStandardTx,multi-op-return) has always been
a block validity rule, the coinbase included. From Napoleon it is gone,
for coinbases and for every other transaction, in blocks and in the mempool
(owner decisions of 2026-11-15;GetMaxDataOutputsForBlockTx). - Only the count is lifted. Unchanged: each OP_RETURN script at most
-datacarriersize(8,005 bytes by default), a transaction at most 100,000
bytes (which also bounds its total OP_RETURN data), the block size, the
signature-check limits; dust is still not checked on OP_RETURN outputs, and
OP_RETURN outputs never enter the UTXO set. Fees are per byte as before. - Before the activation the mempool and the blocks refuse more than 3 exactly
as 12.4.11 does (same reason,multi-op-return). After it such transactions
relay between 12.4.13 nodes only; older nodes refuse to relay them and reject
any block that contains one. - A reorganisation back across the activation drops the many-OP_RETURN
transactions from the mempool, and the block assembler skips any it would
still find, so templates stay valid. - Indexers: eMPP, RANK, POKR, BLOB and the block analytics index every output
(keys includevout); several RANK outputs in one transaction are several
votes. SLP and ALP read only their protocol output (vout[0]), as specified.
UTXO set commitment in the coinbase (mandatory)
Design and research: doc/research/utxo-commitment.md. Owner decision of
2026-11-16: mandatory from Napoleon itself, on mainnet and
testnet.
- What a block must carry. From the first block whose parent's median
time past reaches 1797886200, the coinbase must carry exactly one eMPP
segment"UTXO" | 01 | 01 "M" | u32 h-10 | 32-byte digest
(OP_RETURN OP_RESERVED <push>). It goes either in its own zero-value
output, or appended to an existing eMPP output such as a POOL record. The
digest is the MuHash3072 of the UTXO set after blockh-10, the same
value asgettxoutsetinfo muhashand the UTXO snapshot trailer. - Rejected blocks. A block is rejected if the segment is missing
(bad-utxo-commitment-missing), wrong (bad-utxo-commitment), at the
wrong height (-height), malformed (-malformed) or present twice
(-duplicate). - Before the activation. Nothing is read or written: blocks and
templates are byte-identical to 12.4.11. - Our block paths. Every block path of this node writes it:
generate*,
native, ASIC and aux stratum, the pool coinbase, NNG and external
templates, andcreateauxblock. From Napoleon the OP_RETURN count is not
capped, so the commitment gets an output of its own.
-utxocommitminehas no effect on mainnet or testnet; it only matters on
regtest, where the commitment is optional unless
-utxocommitmentmandatorytimeis given (testnet/regtest only). - Napoleon testnet (
-chain=napoleontest): the commitment is validated
when present from block 1 and mandatory from median time past
1794835800 (2026-11-16 13:30 UTC), so the public testnet chain from
before that (blocks without commitments) syncs without any option. - External miners.
getblocktemplatereturns it in
coinbasetxn.utxocommitment, as a readyscriptPubKey(and as the
segment alone, to append to an eMPP output). - Split risk. A miner or implementation that omits the commitment
produces blocks that 12.4.13 rejects. Nodes that are not on 12.4.13 split
anyway: our coinbases then carry the commitment as one more OP_RETURN
output (a pool coinbase can reach 4), which they reject. - New per-node state. Each node maintains an incremental UTXO set hash.
The first start of 12.4.13 on an existing datadir walks the UTXO set once
to build it: minutes on mainnet, logged as "UTXO hash: computing ...".
It is then kept inchainstate.sqlitewith the coins. - Reading it. RPC
getutxocommitment ( height recheck )and
verifyutxocommitment "muhash" height ( minconf ); REST
/api/v1/chain/utxo-commitment/<height>[?muhash=&minconf=].
getutxocommitment <tip> truechecks the incremental hash against a full
walk of the coins.
Coinbase tag: _ allowed from Napoleon (FRENCH_BTC)
- From Napoleon the coinbase tag (
OP_RETURN <tag> <height>, coinbase
output 0) may contain_as well as ASCII letters and digits, any length
of at least 1, any push opcode, canonical height (owner decision of
2026-11-16: the fleet's tag becomesFRENCH_BTC). - Before Napoleon nothing changes: 5 ASCII letters and digits, pushed
directly, height on 1 to 3 bytes (from height 20,000).FRENCH_BTCis
10 characters with an_, so a node configured with it writes "logos"
until Napoleon (reasonpre-napoleon-needs-5-chars) and no block before
the activation carries it. -coinbasetagnow accepts_(1 to 32 letters, digits and_). The fleet
sets-coinbasetag=FRENCH_BTC -coinbasetagafternapoleon=1; the default
stays "logos" for every other operator.- The rest of the free-form tag after Napoleon (any length, explicit
duplicate-coinbase refusal) is unchanged from earlier releases (owner
decision of 2026-11-14). It was already a split vector against upstream
v12.0.0, which accepts only "logos" after Napoleon.
Mining and pool
Pool activation at median time past 1800000000 (2027-01-15 08:00 UTC),
after Napoleon (owner decision). On mainnet, from that time:
- the exact burn split (option B: no miner is ever overpaid, the rounding
remainder is burnt and recorded in POOL record section "C"); - the payout-script whitelist (P2PKH, P2SH, P2TR and the RANK entity-vote
templates, wire bound 64 bytes) replaces the 40-byte cap.
Before it, every 12.4.13 node builds the 12.4.11 pool coinbase byte for byte.
All fleet nodes must run 12.4.13 (or later) before 2027-01-15, or their
pool ledgers fork. These are pool rules, not consensus: blocks stay valid for
every node either way.
- ASIC listeners (SHA-256d and Scrypt stratum, V1 miners) with upstream
pools over Stratum V1/V2, per-miner upstream accounts (a base64url pool
list in the password, failover and failback, shared upstream connections),
refusal of upstream pools whose extranonce2 cannot hold the anchor. Before
the activation an ASIC listener is at most a plain proxy to its upstream
pool (no Lotus block can come from it); without an upstream pool a
SHA-256d listener refuses connections. - Pool payouts credit ASIC work in the PPLNS window at its Lotus-equivalent
weight (new pool messagespoolauxjob/poolauxshr; an older fleet node
ignores them). PPLNS credit of ASIC work without a Lotus address is burnt
(POOL record section "B"). Every fleet node must run 12.4.13 before an
ASIC listener is opened with pool payouts. - POOL record: up to 16 record outputs from Napoleon (2 before), so a
window with more payees than two outputs can describe (92 at 223 bytes
with the default pool id) is described in full instead of truncated: up
to 820 payees at 223 bytes.getpoolinfo.recordCapacityNapoleon.
Payee outputs were never limited by the OP_RETURN cap (they are not
OP_RETURNs); only the record describing them was. - The 12.4.11 headers pre-sync defers exactly the headers
CheckBlockHeader
defers (a merged-mined header no longer gets its sender banned for
"high-hash" after the activation).
Other changes
- CONTRACT module (opt-in,
-contractindex): Taproot contracts by
commitment, REST and dashboard Contracts tab; contract RPCs and an opt-in
script trace;-scriptcostlog. - Test suite: the whole functional suite is green and gates the release;
test_runnerpicks free port seeds and retries on a taken port. - HTTP server:
TCP_NODELAY(a JSON-RPC round trip drops from about 40 ms to
0.3 ms on kept-alive connections); bodies above 32 MiB only with valid RPC
credentials; RPC timers cancel instead of waiting out. sendrawtransactionapplies the documented defaultmaxfeerate; the
mempool reload applies the policy limits again; SQLite wallets listed by
listwalletdir; index init/shutdown robustness (R-3).- Startup / shutdown page: steady progress bars, the "mining db" step.
Downgrade
Before Napoleon a 12.4.13 node can be rolled back to 12.4.11: the pool
database gains an additive table (aux_jobs) that 12.4.11 ignores, and the
CONTRACT index is a separate opt-in module database. After Napoleon a
rollback leaves the node on the minority chain at the first merged-mined
block, contract spend or transaction with more than 3 OP_RETURNs. The UTXO
hash state 12.4.13 stores in chainstate.sqlite (meta key utxo_hash_state)
is ignored by 12.4.11.
SHA-256 of every file
31fe7d00068f2b23c8b371bec2414b310bbb3742e9d94926c290ce0f44e9c5f6 lotus-binaries-12.4.13-linux-x86_64.tar.gz
4bfc6dfff09da2c849983fbd1c6baedd076b5c6d1df00865c6438d2754433028 lotus-binaries-12.4.13-macos-x86_64.tar.gz
cde9cbd61a9742b4e2d8144212e870c023d6316e1f4bc6f239c8323e2cf7d221 lotus-cli-12.4.13-linux-x86_64.tar.gz
6e66543812fa71d9568982c46f2ebf8f665b9910aea055b34c71a7d69dd92d6f lotus-cli-12.4.13-macos-x86_64.tar.gz
5c21a05e7c167dc85bc92521961d3cb741d62b0638fcabb9f906aeb2cf4f931d lotus-gpu-miner-amd-12.4.13-linux-x86_64.tar.gz
bc4f57265a6e00e302deedd99dca884870e769fdb84e6ff7cf08529c679b9c1d lotus-gpu-miner-nvidia-12.4.13-linux-x86_64.tar.gz
11af5a60cb875f77549fa1db75ffcdb3d34efc6139c530b7413c6189d38c80ff lotus-miner-gui-12.4.13-linux-x86_64.tar.gz
2e58888439ab94b2d504684d1039ba233370c4fed4c4c58057d7b45c89b3341c lotus-seeder-12.4.13-linux-x86_64.tar.gz
ba1aaac09ae68705ad59d1e5db587341a4984093bcf5fda78f7f3cb1968a8066 lotus-seeder-12.4.13-macos-x86_64.tar.gz
b035840ea81f7a489fc502f59121b8e546fcc67644f9a96aefedf7b1066c6463 lotus-tx-12.4.13-linux-x86_64.tar.gz
23ed96832c18580e5fae54232aece2ad03dec5894cbdbb62edd518d48fc54ab3 lotus-tx-12.4.13-macos-x86_64.tar.gz
cbf5c5061a2702aa8172e962d0c4fc1f6ffeec041a57c2a62073cfa66970da19 lotus-wallet-12.4.13-linux-x86_64.tar.gz
1e17e3bfea31bbdfaaed920e6ef58b2e15d74f0baf504fff1b8eb281ae312639 lotus-wallet-12.4.13-macos-x86_64.tar.gz
bcb275bc303598211d78479c4451c4341c65341c6f1152059e28f8720a385b50 lotusd-12.4.13-linux-x86_64.tar.gz
d0555791a027a24251f4902a0281d8aabefe2088f3af20da69fd705c4e569d12 lotusd-12.4.13-macos-x86_64.tar.gz
6e2e66a30ad486961db6bb39419cb278b6d2d3940384cf412c9061e6db4e91bd lotus-binaries-12.4.13-windows-x86_64.zip
b69d6eb7332f60e86f89027744cf6faaf4f16f0b77b240a5a5b92f8eb0c29e0d lotus-cli-12.4.13-windows-x86_64.zip
628a91910549d7dca4781514e808ff5c9c412496849369867a2cf895a66f300c lotus-miner-gui-12.4.13-macos-arm64.zip
b957838d98b94c8bc427ab1da2f1ffebbfd9e5b83b307405ead48f42c7f40aae lotus-miner-gui-12.4.13-macos-universal.zip
0effb3e6f0c869e0dede9966e8faa8986ed53585d5516aff07d92e3192c64416 lotus-miner-gui-12.4.13-macos-x86_64.zip
48769396e78f768aec877f907f955274d57cd4f715bc9335556769dfb2fab54c lotus-miner-gui-12.4.13-windows-x86_64.zip
5561388b57e031af10c831cb4a9c4b6cfeb476fc039f5dc42a3dfe97c4d735cc lotus-tx-12.4.13-windows-x86_64.zip
56d5e5745b1b4be1b486bcc19cca4f118a00bbf206ccb8cbc4d98f4daf1e63dc lotus-wallet-12.4.13-windows-x86_64.zip
4dbb042b1cc17a43f4d10b69156d2f5e126faa7e982a12f6fc3e5e53a8ecad6f lotusd-12.4.13-windows-x86_64.zip
Consensus changes: yes. New rules activate at Napoleon, when the median time past of the previous block reaches 1797886200 (2026-12-21 20:50 UTC) · Minimum version on the network: 12.4.13, required from Napoleon (2026-12-21 20:50 UTC)
Install and upgrade guide · Web wallet · All releases · Container images · Report a problem