Install a node
Download lotusd 12.4.15 for Linux, macOS or Windows, verify the checksums, or pull the Docker image.
A Lotus node is one program, lotusd, with a command-line client, lotus-cli. Releases are published on github.com/LotusDevOrg/lotusd-releases; the Downloads page lists the same files with their sizes and checksums.
Download from that repository and nowhere else. The files are not signed: the checksum file is what you verify.
What a release contains #
Every file is named <name>-<version>-<os>-<arch>, as .tar.gz (.zip on Windows).
| Archive | Linux x86_64 | macOS x86_64 | Windows x86_64 |
|---|---|---|---|
lotus-binaries (node and tools in one archive) | yes | yes | yes |
lotusd (the node alone) | yes | yes | yes |
lotus-cli, lotus-tx, lotus-wallet | yes | yes | yes |
lotus-seeder | yes | yes | no |
SHA256SUMS lists the SHA-256 of every file of the release. Take lotus-binaries unless you know you need less.
Linux #
V=12.4.15
BASE=https://github.com/LotusDevOrg/lotusd-releases/releases/download/v$V
curl -fsSLO $BASE/SHA256SUMS
curl -fsSLO $BASE/lotus-binaries-$V-linux-x86_64.tar.gz
sha256sum -c --ignore-missing SHA256SUMS
tar -xzf lotus-binaries-$V-linux-x86_64.tar.gz
./lotus-binaries-$V-linux-x86_64/lotusd -versionsha256sum must print OK for the archive. Copy the binaries where you keep them, for example /usr/local/bin.
macOS #
The same steps with the macOS archive and shasum:
V=12.4.15
BASE=https://github.com/LotusDevOrg/lotusd-releases/releases/download/v$V
curl -fsSLO $BASE/SHA256SUMS
curl -fsSLO $BASE/lotus-binaries-$V-macos-x86_64.tar.gz
shasum -a 256 -c --ignore-missing SHA256SUMS
tar -xzf lotus-binaries-$V-macos-x86_64.tar.gzThe binaries are built for Intel Macs and are not notarised by Apple: macOS asks for confirmation before the first launch.
Windows #
Download lotus-binaries-12.4.15-windows-x86_64.zip and SHA256SUMS from the release page. In PowerShell:
Get-FileHash .\lotus-binaries-12.4.15-windows-x86_64.zip -Algorithm SHA256The value must be the one on that file's line in SHA256SUMS. Then unzip.
Docker #
The node image is ghcr.io/lotusdevorg/lotusd. Each release is pushed under three tags: the exact version (12.4.15), its line (12.4, which follows the newest release of that line) and latest.
docker pull ghcr.io/lotusdevorg/lotusd:12.4.15Pull an exact version, so that an upgrade is something you decide. The release notes give the image digest; ghcr.io/lotusdevorg/lotusd@sha256:... pins the exact image.
The image contains lotusd only. Its entrypoint is lotusd, started with -printtoconsole -datadir=/root/.lotus, and it exposes the P2P port 10605 and the RPC and web port 10604. Mount a volume on /root/.lotus to keep the chain data:
docker run -d --name lotusd \
-v lotus-data:/root/.lotus \
-p 10605:10605 \
ghcr.io/lotusdevorg/lotusd:12.4.15lotus-cli is a separate image, ghcr.io/lotusdevorg/lotus-cli, as are lotus-tx, lotus-wallet and lotus-seeder.
Inside the container the RPC and web port listens on localhost only, like any node. Publishing port 10604 to the host is not enough to reach the dashboard: see Docker for the bind options and a compose file.
Build from source #
The build instructions are in the source tree: doc/build-unix.md (Linux and other Unix systems), doc/build-osx.md (macOS) and doc/build-windows.md (Windows), with INSTALL.md as the entry point. The build system is CMake.
Data directory #
lotusd keeps the chain, its indexes, the wallets and the log in one data directory:
| System | Default data directory |
|---|---|
| Linux | ~/.lotus/ |
| macOS | ~/Library/Application Support/Lotus/ |
| Windows | %APPDATA%\Lotus\ |
Pass -datadir=<dir> to use another one. Mainnet data sits directly in it; the other networks use a subdirectory: testnet3/, regtest/ or napoleontest/.
The configuration file is lotus.conf in the data directory. It is not created for you: see Configuration.
A full mainnet node with the explorer index needs tens of gigabytes: the explorer database alone was 32.8 GB at height 1,425,360. A node started with -explorerindex=0 needs an estimated 3 to 4 GB. Thin mode needs less.
Next #
- Run the node: first start, ports, how to check it.
- Upgrade: move an existing node to 12.4.15.
- Napoleon: every node must run 12.4.13 or later before 21 December 2026.
