How to Run Your Own Litecoin Node

Litecoin Core is a direct fork of Bitcoin Core, so if you’ve run a Bitcoin node this will feel familiar — but it’s its own chain: Scrypt proof-of-work, 2.5-minute blocks(4× faster than Bitcoin), an 84M coin cap, and the MWEB (MimbleWimble Extension Blocks) confidential-transaction upgrade. It’s also much lighter to run. This is the exact litecoind setup we run in production on Ubuntu 24.04, including the optional address-indexed API layer.

Hardware & disk requirements

Litecoin’s chain is a fraction of Bitcoin’s — but you still want an NVMe SSD for the random-I/O chainstate, especially if you add the address index. The full chain with txindex is ~150 GB and growing.

Step 1 — Download and verify Litecoin Core

Get the binary from the official litecoin-project releases (or the download.litecoin.org mirror) and check it against the published SHA256SUMS. Set VER to the current release (we run 0.21.5.5):

VER=0.21.5.5
cd /tmp
curl -LO https://github.com/litecoin-project/litecoin/releases/download/v$VER/litecoin-$VER-x86_64-linux-gnu.tar.gz
curl -LO https://github.com/litecoin-project/litecoin/releases/download/v$VER/SHA256SUMS.asc

sha256sum --ignore-missing --check SHA256SUMS.asc
# -> litecoin-$VER-x86_64-linux-gnu.tar.gz: OK

tar xzf litecoin-$VER-x86_64-linux-gnu.tar.gz
sudo install -m755 litecoin-$VER/bin/litecoind litecoin-$VER/bin/litecoin-cli /usr/local/bin/
litecoind --version | head -1

Step 2 — Dedicated user, data dir, and config

sudo useradd --system --no-create-home --shell /usr/sbin/nologin litecoin
sudo mkdir -p /var/lib/litecoin /etc/litecoin
sudo chown litecoin:litecoin /var/lib/litecoin
openssl rand -hex 32   # <- use as rpcpassword below

Create /etc/litecoin/litecoin.conf. Litecoin’s default RPC port is 9332(P2P is 9333). The config is essentially identical to Bitcoin’s — the ZMQ feeds are only needed if you add Blockbook in Step 5:

server=1
disablewallet=1
txindex=1
prune=0

dbcache=1024
maxmempool=300
listen=1
maxconnections=64

rpcbind=127.0.0.1
rpcallowip=127.0.0.1
rpcport=9332
rpcuser=litecoin
rpcpassword=<PASTE_THE_GENERATED_PASSWORD>
rpcthreads=8
rpcworkqueue=64

datadir=/var/lib/litecoin

# ZMQ feeds (only needed for an indexer like Blockbook):
zmqpubhashblock=tcp://127.0.0.1:38331
zmqpubrawblock=tcp://127.0.0.1:38331
zmqpubhashtx=tcp://127.0.0.1:38331
zmqpubrawtx=tcp://127.0.0.1:38331

Same permissions gotcha as Bitcoin — the litecoin user must be able to read the config:

sudo chown -R root:litecoin /etc/litecoin
sudo chmod 750 /etc/litecoin && sudo chmod 640 /etc/litecoin/litecoin.conf

Step 3 — systemd service

[Unit]
Description=Litecoin Core daemon
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=litecoin
Group=litecoin
ExecStart=/usr/local/bin/litecoind -conf=/etc/litecoin/litecoin.conf
Restart=on-failure
RestartSec=10
TimeoutStartSec=infinity
TimeoutStopSec=300
PrivateTmp=true
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

Step 4 — Start and watch the sync

sudo systemctl daemon-reload
sudo systemctl enable --now litecoind

litecoin-cli -conf=/etc/litecoin/litecoin.conf getblockchaininfo \
  | grep -E '"blocks"|"headers"|"verificationprogress"|"size_on_disk"'
litecoin-cli -conf=/etc/litecoin/litecoin.conf getblockcount

With its smaller chain, Litecoin’s initial block download finishes in under a day on NVMe. When verificationprogress hits 0.9999…you’re at the tip — point your apps at http://127.0.0.1:9332.

Step 5 (optional) — Address-indexed API with Blockbook

Just like Bitcoin, litecoind has no address index— it can’t answer “what’s the balance and history of address X?” on its own. To serve address/xpub queries and a REST + WebSocket API, run an indexer alongside it. Blockbook supports Litecoin out of the box; it reads from your synced litecoind over RPC + the ZMQ feeds and builds its own ~150 GB index. The setup is identical to the Bitcoin guide’s Blockbook section — including the runtime libraries and the memory-cap drop-in that prevents an OOM kill from corrupting the index mid-build.

The honest part: what running it actually costs

• Litecoin is the easy one — but it’s still a node you have to keep synced, patched at every Litecoin Core release, and monitored 24/7.
• Address queries still need a second system. The index is another ~150 GB and its own sync, and it reindexes from scratch if it’s ever OOM-killed mid-write.
• One node is a single point of failure. Real uptime means redundancy + a load balancer — and it’s rarely just Litecoin you need; every additional chain is another full stack.
• The real bill is engineer-hours, not the server — see Self-Hosted Node vs RPC Provider.