Running a Litecoin full node: setup, pruning and troubleshooting

In brief A peer-to-peer cryptocurrency with its own Scrypt proof-of-work network and a maximum issuance of 84 million LTC.

A peer-to-peer cryptocurrency launched in 2011. Litecoin uses Scrypt proof of work, targets an average 2.5-minute block interval and has an issuance schedule capped at 84 million LTC. Individual block times and payment acceptance times vary.

For example Sending 0.1 LTC on Litecoin transfers a fraction of one coin; you do not need to buy a whole LTC first.

Common mistake Assuming a token with LTC in its name on another network is automatically native Litecoin.

In brief A participant running network software; a full node checks rules but need not keep all old block files.

A participant running network software. A full node independently validates rules; a pruned full node can discard older block files after validation. Not every node stores the complete historical blockchain.

For example A pruned full node checks the chain but later discards old block files to reduce disk use.

Common mistake Assuming every node is a miner, or that pruning means it skipped consensus validation.

In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.

Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.

For example One wallet can generate several receiving addresses and still show them as a single combined balance.

Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.

In brief A group of transactions linked to the previous block under the network's rules.

A batch of transactions accepted under the network rules and linked to the previous block. Litecoin targets one new block every 2.5 minutes on average; a particular block may arrive sooner or much later.

For example Your payment may wait unconfirmed and then receive its first confirmation when a miner includes it in an accepted block.

Common mistake Treating the 2.5-minute target as a countdown or a maximum wait for your payment.

In brief A wallet's search of available blocks for matching transactions; blockchain data cannot replace missing recovery secrets.

A wallet's search through available blocks for transactions matching its keys or scripts. The scan needs the intended wallet configuration and readable history for the relevant period. It discovers transaction records; it cannot recover missing secret root material or an unrelated private key from blockchain data.

For example After importing the intended wallet material, a scan that covers the old receipt's block may discover that transaction.

Common mistake Scanning only recent retained blocks and assuming completion proves an old wallet's whole history was recovered.

In brief Deleting older block files after validation to save disk space, which can limit later rescans of old transactions.

A full node's deletion of older block files after validating them to reduce disk use. It still checks consensus rules and keeps current chain state, but the deleted history is unavailable for an ordinary local rescan. A pruning target is not a budget for the entire application.

For example A node can validate today's chain while lacking the old blocks needed to rescan a payment from years ago.

Common mistake Assuming pruning skips validation, or that switching it off instantly restores deleted historical block data.

In brief The rules nodes use to check transactions and blocks, with Litecoin using proof of work to choose among valid chains.

Rules used by nodes to decide which transactions and blocks are valid. Litecoin uses proof of work to select among valid chains. Miners propose blocks, but validating nodes also enforce the rules.

For example A full node rejects a block that breaks its validation rules even when a miner has done proof-of-work calculations.

Common mistake Thinking that miners can make any transaction valid merely by including it in a block.

In brief Who controls spending access; with a custodial service, the provider controls the keys behind your account.

Who controls the signing material and the process for moving funds. With a custodial service, the provider controls the relevant keys and you use an account. Self-custody places key and backup responsibility with you; an account password is not a private key.

For example An exchange withdrawal moves funds from the provider's control to an address whose signing keys your own wallet controls.

Common mistake Assuming an exchange balance and a self-custody wallet offer the same control, recovery process or withdrawal availability.

In brief For transparent Litecoin, a node's record of unspent outputs, separate from wallet keys and full transaction history.

A node's compact record of the currently unspent outputs and associated state for its accepted chain. For ordinary transparent Litecoin, it helps answer whether a particular output remains unspent. It is different from wallet keys and the full historical block files.

For example An output can remain in historical transaction data after it has been spent and removed from the current UTXO view.

Common mistake Treating the chainstate database as a wallet backup or assuming it lists every payment ever made to an address.

In brief Litecoin's optional layer that conceals amounts inside it, while base-chain and boundary activity can still reveal information.

Mimblewimble Extension Blocks, activated on Litecoin in May 2022. MWEB conceals amounts inside the extension layer; the base chain and boundary transfers can reveal information. Use maintained software and review the 2026 security postmortem.

For example An MWEB transfer uses compatible software and a different address format from an ordinary transparent Litecoin transfer.

Common mistake Assuming every LTC wallet or exchange accepts MWEB addresses, or that optional privacy removes all possible information leaks.

In brief A linked record of transaction blocks that Litecoin nodes validate, choosing a valid chain by accumulated mining work.

A ledger of cryptographically linked blocks. Litecoin full nodes validate proposed blocks against consensus rules and select among valid chains by accumulated proof of work. Recent blocks can be reorganized, so confirmation depth matters.

For example A block explorer reads the chain so you can inspect where a transparent transaction was included.

Common mistake Assuming an explorer listing proves the sender's identity or that a recent block can never be replaced.

In brief Secret data a wallet uses to sign spending; one key may cover only part of a wallet and must never be shared.

Secret data used to authorize spending under the conditions attached to coins. In a simple single-key wallet, anyone with that key can spend the coins it controls. A wallet may manage many keys; never share them.

For example A wallet signs a spend using a private key; the recipient only needs your payment, not that secret key.

Common mistake Sharing a key with support or assuming one exported key necessarily backs up every address in a wallet.

In brief A cryptographic hash function used twice in Bitcoin mining; Litecoin mining uses Scrypt but still uses SHA-256 elsewhere.

A cryptographic hash function producing a 256-bit digest. Bitcoin mining uses a double-SHA-256 construction; Litecoin proof of work uses Scrypt. Litecoin nevertheless uses SHA-256-based functions elsewhere, including transaction and block identification.

For example A Bitcoin mining device advertises SHA-256 hash power, while Litecoin mining hardware advertises Scrypt hash power.

Common mistake Assuming Litecoin does not use SHA-256 anywhere simply because its proof-of-work algorithm is Scrypt.

In brief Secret recovery words that need the right wallet format, settings and any extra passphrase; keep them offline.

A sequence of secret recovery words that some wallets use to rebuild keys. Recovery must match the original wallet's word format, settings and any extra passphrase; other wallets use different backup methods. Keep the words offline and follow the original wallet's official recovery instructions.

For example In a BIP39 wallet, the same words with a different extra passphrase produce a different seed and can show different addresses.

Common mistake Entering recovery words into a website, sharing them with support or assuming every Litecoin wallet uses the same word format.

In brief Recovery material for a specific wallet and format, whose coverage depends on when and how the backup was made.

A recovery copy of the material needed for a particular wallet, such as its wallet file and required configuration. Coverage depends on the format and when it was made; later imported keys may require a fresh backup.

For example A Core wallet-file backup made before a separate key import can omit that imported key.

Common mistake Treating a receiving-address list as a spending backup, or assuming every wallet file can be restored by another application.

In brief Searching for valid proof of work and proposing Litecoin blocks that other nodes independently check.

Searching for proof of work and assembling candidate blocks that follow a network's rules. Validating nodes independently check proposed blocks. An accepted Litecoin block can pay its miner the permitted subsidy and transaction fees; a pool participant is paid under the pool's scheme.

For example An ASIC connected to a pool contributes proof-of-work attempts; the pool pays according to its published scheme.

Common mistake Comparing coin revenue without subtracting electricity, pool charges, downtime and equipment costs.