Recovering a Litecoin wallet: identify the backup before restoring

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 recovery-word standard used by some wallets to derive a seed from the words and an optional passphrase.

A specification that turns generated randomness into recovery words and derives a seed from those words plus an optional passphrase. It does not define every wallet's backup format or the complete address-discovery process. Not every recovery phrase is BIP39.

For example The same BIP39 words with two different passphrases produce different seeds and can open different wallets.

Common mistake Assuming twelve words identify the format, or that every Litecoin app will restore the intended accounts from those words alone.

In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.

An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.

For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.

Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.

In brief A wallet-specific secret that can unlock stored keys or change the seed derived from recovery words.

A secret whose role depends on the wallet. A local encryption passphrase unlocks stored signing material. A BIP39 recovery passphrase is combined with recovery words to derive a seed. Changing the local unlock password does not by itself change that BIP39 recovery setup or move coins.

For example A typo in a BIP39 passphrase can derive a different valid wallet, whereas a wrong local encryption passphrase normally fails to unlock the file.

Common mistake Treating an app password, device PIN and recovery passphrase as interchangeable, or assuming a password change invalidates every old backup.

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 A spending rule requiring a set number of key signatures, with the wallet policy also needed for recovery.

A spending policy requiring signatures from a stated number of keys, such as two of three. Recovery also needs the correct script or wallet policy and enough signing keys; one cosigner's seed is not necessarily sufficient.

For example In a 2-of-3 policy, any two of the three authorized keys can satisfy the signing threshold.

Common mistake Keeping enough seeds but losing the script or key-order information needed to reconstruct the wallet.

In brief A device designed to keep signing keys isolated while approving supported transactions, still requiring safe setup and backups.

A dedicated device designed to isolate signing keys and approve transactions through its supported interface. It still depends on correct setup, backups, supported software and careful review of the recipient and amount. Coins remain recorded on the blockchain.

For example A connected app prepares a payment while the hardware device displays details for you to verify before authorizing a signature.

Common mistake Assuming owning the device makes an exposed recovery phrase safe or removes the need to check what you authorize.

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 SegWit output wrapped in P2SH, with the fee tool's nested option limited to the single-key P2SH-P2WPKH type.

A SegWit witness program wrapped inside a P2SH output. For the site's fee estimator, nested specifically means P2SH-P2WPKH, the single-key construction. It retains extra P2SH wrapping data compared with native P2WPKH. Other P2SH constructions need different assumptions.

For example A wallet identifying an input as P2SH-P2WPKH supplies enough information to use the nested input option; an M-prefixed address alone does not.

Common mistake Treating nested SegWit as native Bech32 or assuming that the word P2SH always means P2SH-P2WPKH.

In brief A transaction format and validation change that separates witness data and changes how block capacity is counted.

Segregated Witness: a change to transaction serialization and validation that separates witness data, fixes certain transaction-malleability issues and changes capacity accounting. Litecoin activated it in May 2017.

For example An ltc1q receiving address uses a SegWit format; the sender still needs to check that its service accepts that address.

Common mistake Assuming every wallet supports every address format, or that SegWit guarantees a fixed confirmation time.

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 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 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 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 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 service for trading currencies or assets, whose custodial account balance does not give you control of its private keys.

A platform or service for buying and selling cryptocurrencies against fiat currencies or other assets. Trading methods, custody, supported pairs and withdrawal rules vary by service. A balance on a custodial exchange is an account claim; it does not mean you control the wallet's private keys.

For example After buying LTC on a custodial exchange, you request a withdrawal if you want it sent to your own wallet.

Common mistake Assuming an account balance means you possess the private keys, or overlooking the selected withdrawal network.