Litecoin address formats explained: legacy, SegWit, Bech32, and MWEB

A Litecoin address encodes a destination under a network's rules. Its prefix helps identify the format, but it is not proof that the sender supports that format, that the recipient is trustworthy or that a transfer will be private.

The full address and its checksum matter. Never convert an address by manually replacing its first characters.

Common mainnet formats

These are mainnet prefixes, not complete sample addresses. Core's encoding implementation and network parameters are the technical references.

A prefix is not a complete fee model

An M-address can encode a script with different spending requirements. A native witness address may reduce the weight of some common spends, but the fee depends on input count, output count, script type and chosen fee rate.

A transfer spending many small outputs can cost more than a simple transfer even if both use an efficient receiving format. Comparing fees by address prefix alone hides this structure.

These are arithmetic examples, not size guarantees for address types. A litoshi is one hundred-millionth of LTC.

Compatibility is a two-sided question

The receiving wallet must control the destination and the sender must support constructing a valid payment to it. Exchanges may impose narrower policies than the underlying protocol.

If a sender rejects your address, generate a supported receiving format in your wallet or ask the provider about support. Do not paste the address into an unknown online converter or edit the prefix. Preserve the intended network; similarly shaped addresses do not make Bitcoin and Litecoin interchangeable.

A wallet update can change defaults. Verify the address on the receiving device and perform a small test when using a new route.

MWEB changes visibility

MWEB supports confidential internal transfers, but transparent entry and exit information and external account records remain relevant. An ordinary explorer cannot show every private amount or identify the recipient from a public MWEB address list. MWEB specification.

The old table's “full privacy” label and blanket wallet-support claim were too strong. Confirm the exact application version and destination integration. A provider supporting ordinary LTC deposits may decline MWEB.

Address hygiene matters across formats

Use a fresh address when practical to reduce direct reuse. That does not defeat all transaction clustering. Do not post invoice addresses and identity details publicly unless disclosure is intended.

Compare the entire destination using a trusted display. Never copy a receiving address from unsolicited transaction history. The scam guide explains poisoning and clipboard attacks.

What to do after a wrong-network transfer

Preserve the transaction reference and contact the actual receiving provider through a verified channel. Recovery depends on who controls the relevant keys, scripts, network and service policy. Do not promise recovery solely because two address formats look related.

Do not reveal a recovery phrase to someone offering help. A legitimate support process should not require giving a stranger control of all wallet assets.

Frequently asked questions

Is ltc1p universally supported?

No. Check the specific sender, receiver and version rather than inferring support from the prefix.

Does changing my receiving format move old coins?

No. Existing outputs retain their original spending conditions until spent. Creating a new address is not a retroactive conversion.

Where can I inspect a transparent payment?

Use the block explorer guide and confirm the actual output, not just the address's appearance.