Dotted-underlined terms open a quick definition. Close it to keep reading.
Use an generated by the intended receiver, on the intended , through a route both support. A recognizable prefix is only the beginning of that check. It does not identify the owner, prove a deposit will be credited or establish what a later spend will cost.
Expanded review · 22 October 2026. Format descriptions use Litecoin Core 0.21.5.8. The examples reuse our 3 October controlled address-decoding study: 18 synthetic fixtures and 36 RPC observations, with disconnected mainnet-mode and regtest . There was no transfer, synchronized-chain observation, service-credit test or MWEB wallet test.
Common mainnet formats
Recognizable Litecoin mainnet families; prefixes alone do not prove the complete route is supported.
Visible form
What it describes
Important qualification
L…
Base58Check P2PKH destination
Legacy transparent key-hash output
M…
Modern Litecoin Base58Check P2SH destination
Can wrap witness or other redeem scripts
3…
Historical version-5 P2SH encoding
Overlaps Bitcoin's familiar form; chain remains a separate choice
ltc1q…
Witness version 0, Bech32
Can encode a key-hash or script-hash program
ltc1p…
Witness version 1, Bech32m
Often associated with Taproot; require explicit wallet support
ltcmweb1…
MWEB receiving address
Requires an explicitly supported MWEB workflow
The network parameters define Litecoin's version bytes and human-readable prefixes. The address encoder and decoder map them to destinations. Core accepts both historical and modern versions, while generating the modern form. This compatibility does not require every service to accept both.
“ address” is not one unique family. P2SH may wrap a witness program; native witness addresses encode it directly. Likewise, the first witness-version character does not by itself establish the program's length, every spending rule or the sending wallet's capabilities. In particular, do not promise universal support from an ltc1p prefix.
Checksums, networks and ownership answer different questions
Base58Check and -family encodings contain error-detection checksums. A valid checksum can catch many transcription errors; it cannot tell whether an attacker supplied a different valid destination. The decoder must also accept the network, version, program length and checksum family.
BIP 173 defines the Bech32 family and case rules. BIP 350 specifies Bech32m for witness versions 1 and later; version 0 retains Bech32. For ordinary witness addresses, all-lowercase and all-uppercase representations can be valid, while mixed case is rejected. Base58 strings are case-sensitive and do not follow that conversion rule.
Selected recorded Core 0.21.5.8 results; fixtures are test data and must never receive funds.
Synthetic case
Mainnet-mode result
Meaning and limit
Modern M and historical 3, identical script-hash payload
Both valid; identical output scripts
Encoding compatibility, not ownership or cross-chain recovery
Ordinary ltc1q fixture
Valid
Syntax and destination accepted under these parameters
Different valid ltc1q payload
Also valid
A valid substituted destination still passes parsing
All-uppercase / mixed-case Bech32 fixture
Valid / invalid
Case rules are format-specific
One checksum-character typo
Invalid
The particular Base58 and Bech32 changes were detected
bc1, tltc1 or rltc1 fixture
Invalid
Wrong human-readable prefix for Litecoin mainnet
Complete litecoin: payment URI
Invalid as a bare address
A URI parser must extract and check its fields first
The regtest node accepted the appropriate regtest forms instead. “Mainnet mode” here describes decoder parameters at height zero with no peers. It does not mean the fixtures were used on the live chain. Download the 36 recorded observations and method and limits; full fixture strings are explicitly labeled “do not send”. The study did not exercise witness-v1 or destinations.
A prefix is not a complete fee model
The destination determines the output script being created. Future fees also depend on the scripts of the inputs spent, input count, change, signatures and selected . Switching today's receiving format does not rewrite existing outputs: spending or moving them requires a new transaction.
A historical 3 and modern M encoding of the same script hash can create the same P2SH output. Renaming that encoding does not turn an arbitrary redeem script into native SegWit or reduce its spending data. The address also cannot reveal the entire redeem script hidden behind its hash.
Compare final wallet previews for equivalent payments rather than assigning one permanent fee to each prefix. For example, the same hypothetical 200 vB at 2 /vB costs 400 litoshis regardless of the amount sent. That illustration is not a measured P2SH, Taproot or MWEB size. The fee guide supplies actual archived signed-size cases and explains RPC units.
Compatibility is a two-sided question
Check four layers before paying: the chain selected by the sender, the destination's encoding, the sender's ability to construct that transaction, and the receiver's ability or willingness to recognize and spend the result. A can impose narrower rules than the underlying protocol. A successful address-decoding check cannot substitute for its deposit instructions.
Open a fresh receiving request in the intended wallet or provider account. Confirm the asset and actual network name.
Read supported formats, minimum deposits and any route-specific restrictions. Resolve uncertainty with the receiver before sending.
Paste or scan the complete request. Inspect any 's destination and amount in the wallet's own preview.
Authenticate the complete address through the intended channel, and review it on the signer's trusted display when available.
If the receiver recommends a small trial, ensure it exceeds applicable minimums and verify actual credit before the remainder. A trial costs money and does not guarantee future compatibility.
Do not “repair” a rejected address by changing its visible prefix. That changes the encoded data without the required checksum and may misunderstand the destination. Historical P2SH re-encoding requires preserving the exact script hash and recomputing the checksum; use only a verified, explicitly supported workflow. An unknown web converter adds another place for address substitution.
MWEB changes visibility
An MWEB receiving address is not an ordinary transparent output with a cosmetic prefix. The MWEB design describes extension- transactions and their confidentiality model. Wallet support and or peg-out handling matter to the route.
Confirm explicit MWEB support at both ends. A provider that accepts ordinary Litecoin mainnet deposits may still decline that workflow. Do not send to a generic deposit page on the assumption that every LTC route is interchangeable. Moving funds across visibility boundaries can reveal information at entry and exit; software, network metadata and a counterparty's records remain relevant. MWEB is not a promise of anonymity against every observer.
The address-decoding experiment above did not test MWEB transfer behavior. Use the MWEB learning path and a specific wallet's current documentation for that separate workflow.
Address hygiene matters across formats
Generate new receiving requests when your wallet supports them, keep useful private labels and verify the whole destination. An address copied from transaction history may belong to change, a previous counterparty or an attacker imitating familiar leading and trailing characters. A checksum does not authenticate your intended recipient.
Fresh addresses can reduce straightforward , but do not erase public links created when transparent inputs are later spent together. See the dusting and address-poisoning guide and the cold-storage recovery checks. Never disclose to an address checker; address validation does not require them.
What to do after a wrong-network transfer
Record the , actual chain used, full destination, time and the receiver's deposit instructions. Establish whether anything was broadcast and confirmed. If it is still only a withdrawal request, the provider's cancellation process may matter more than tools.
After , the possible recovery depends on the actual output conditions, who controls the necessary keys or scripts, and the custodian's procedures. A visually similar address or shared script-hash version does not establish that a particular service can or will recover it. Sending more funds or importing a seed into a “recovery” website cannot reverse history. Follow the wrong-network guide for evidence to collect and the boundaries of its controlled tests.
Use this guide
Download the address and route checklist. It separates checksum, network, wallet support, receiver policy and destination authentication. Use payment route information and the MWEB wallet filter to narrow your investigation, then check the chosen provider's current instructions. Neither directory is a guarantee for a specific deposit.
Frequently asked questions
Are all M addresses wrapped SegWit?
No. M identifies the modern Litecoin P2SH encoding. The underlying redeem script can represent different spending arrangements.
Can a 3 address be valid for Litecoin?
Yes. Core accepts the historical P2SH version. Its overlap with a familiar Bitcoin form makes the chain selection and receiver's instructions especially important.
Does a valid checksum prove I have the right recipient?
No. Another valid address can pass every syntax check. Authenticate the complete destination separately.
Is ltc1p universally supported?
No. It denotes witness version 1 with Bech32m encoding. Confirm the particular sender, receiver and spending workflow explicitly.
Does changing my receiving format move old coins?
No. Existing outputs retain their scripts. Moving their value requires spending them in a new transaction with its own fee and privacy consequences.
Can I send MWEB to every LTC exchange deposit?
No. Use an explicitly supported MWEB route. General Litecoin deposit support does not establish MWEB support.
Address
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 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 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 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 An output that locks coins to a script hash, so its address alone does not reveal the full spending rules.
A transparent output type that commits to a spending script through its hash. The spender supplies the redeem script and the data needed to satisfy it. P2SH can wrap different conditions, including multisignature arrangements and nested SegWit; the address format alone does not identify the exact spending conditions.
For example A P2SH output can contain P2SH-P2WPKH, but a wallet must identify that construction before you use the nested single-key fee model.
Common mistake Treating every P2SH output as nested SegWit or assuming that all P2SH inputs have the same size.
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 An error-detecting address format for Litecoin's version-0 SegWit addresses, distinct from Bech32m for later versions.
An address encoding with an error-detecting checksum. Litecoin's native witness-version-0 addresses use Bech32 and begin ltc1q on mainnet. Later witness versions use the related Bech32m encoding. A valid checksum does not identify the owner or guarantee wallet support.
For example A wallet can recognize an ltc1q address while an older sending service still refuses that format.
Common mistake Treating every ltc1 address as the same script type or assuming a valid address guarantees that a service will credit the payment.
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 fee per unit of transaction size, rather than the total charge, with MWEB using additional accounting.
A fee per unit of transaction size, rather than the total charge. For ordinary transparent Litecoin, wallets commonly quote litoshis per virtual byte. The estimated total depends on both that rate and the transaction's virtual size; MWEB adds different accounting.
For example An illustrative 200-vB transaction at 2 litoshis/vB costs 400 litoshis, while a 400-vB transaction at that rate costs 800.
Common mistake Reading 2 litoshis/vB as a 2-litoshi total, or assuming a recommended rate guarantees a confirmation time.
In brief An informal name for 0.00000001 LTC, the smallest Litecoin unit, with 100,000,000 in one LTC.
An informal name for the smallest Litecoin unit: 0.00000001 LTC. One LTC contains 100,000,000 litoshis. Some software uses the inherited label satoshi, so always check which coin and unit a screen means.
For example 10,000 litoshis equal 0.0001 LTC; 1 litoshi equals 0.00000001 LTC.
Common mistake Confusing a fee quoted per virtual byte with that many litoshis for the whole transaction.
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 Text, often encoded as a QR code, that requests a payment but does not send coins or prove the recipient's identity.
Structured request text, often inside a QR code, containing a destination and optional payment fields. Many Litecoin requests use the litecoin: scheme. Bitcoin's older BIP21 format provides background, but supported addresses, amounts and parameters depend on the actual Litecoin wallet.
For example The placeholder litecoin:ADDRESS?amount=0.1 requests 0.1 LTC; it does not send coins or prove that the named recipient controls the address.
Common mistake Assuming a QR code authenticates a merchant or that every wallet interprets optional fields and expiry information the same way.
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 Moving Litecoin from transparent mainchain addresses into private MWEB outputs (peg-in) and back out (peg-out).
Bridge operations connecting Litecoin's transparent base layer and optional Mimblewimble Extension Blocks (MWEB). A peg-in locks transparent coins and creates a confidential MWEB output, while a peg-out moves an MWEB balance back onto a standard L, M or ltc1 address.
For example Before depositing LTC to an exchange that only accepts ltc1q addresses, a user pegs out from MWEB into a transparent self-custody address first.
Common mistake Assuming peg-in or peg-out amounts remain hidden on-chain; only transfers strictly inside MWEB conceal values.
In brief Receiving multiple payments at one address, which can link transparent payment records.
Receiving multiple payments at the same address. For transparent Litecoin payments, this can link receipts and complicate invoice matching. A fresh receiving address helps separate payment records, but does not by itself make a transaction anonymous.
For example Two invoices using one receiving address need another reliable identifier to distinguish their payments.
Common mistake Believing that reusing an address is required to keep funds in one wallet, or that fresh addresses guarantee anonymity.
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.
Compare: Seed phrase vs private key
Seed Phrase
Recovery words used by many wallets to rebuild key material; the correct format, optional recovery passphrase and wallet settings still matter.
Private Key
A secret used to authorize spending under its key conditions; one exported private key is not necessarily a backup of every key a wallet uses.
One example A fictional simple HD wallet can derive several receiving keys from one recovery setup; exporting just one of those private keys does not preserve the others.
Remember: Identify the complete backup method for the original wallet, keep secret recovery material offline and never paste it into this website.
In brief A transaction identifier for looking up outputs and confirmations, which alone does not prove that a payment arrived.
The identifier used to look up a transaction. For an ordinary transparent Litecoin transaction it is shown as a 64-character hexadecimal string. Use it to inspect the transaction's outputs and confirmations; the ID alone does not prove a payment is confirmed.
For example Copy the TXID from your wallet's payment details into a Litecoin explorer to check the recipient output and confirmation count.
Common mistake Sharing a seed phrase to trace a payment, or treating a screenshot or TXID alone as proof that the expected amount arrived.
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 A transaction gains confirmations as blocks build on its inclusion, but those confirmations can fall if chain history changes.
A transaction receives its first confirmation when included in a block in the accepted chain. Each block then built on top adds another. A chain reorganization can reduce or remove the count. The recipient decides how many confirmations it requires. Litecoin targets an average 2.5-minute block interval; individual blocks can arrive sooner or much later.
For example A transaction in the latest accepted block has one confirmation; the next block raises that count to two.
Common mistake Confusing a wallet's sent message, a TXID or mempool visibility with the first confirmation.
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.
Content review recorded: 2026-10-22. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.