Step-by-step

  1. Open Receive and select Litecoin. Copy the ltc1 string. Tell the sender “Litecoin mainnet”, not Bitcoin and not an EVM net.
  2. Wait for confirmations on litecoinspace. History uses a public Esplora-compatible API (litecoinspace.org) through the adapter. We do not show fake instant credits.
  3. Keep LTC for the next send’s fee. Send uses live fee rates. There is no Litecoin corridor in Exchange.
Bitcoin address kind

GaurdWallet HD accounts are BIP-84 P2WPKH (bc1…). You can still send to legacy 1… / 3… addresses; this wallet will not re-derive those from the seed.

ltc1 vs legacy L

Same design as Bitcoin’s bc1 vs 1…, different HRP (ltc) and coin type 2. Paying an L-address from Send is paying their script if validation accepts it. Recovering an L-account from this seed is not something Receive will suddenly do.

FormatGaurdWallet HD Receive
ltc1… P2WPKHYes
L… P2PKHNo
M… P2SH (older)No
bc1… BitcoinWrong coin — Bitcoin network
Warning

Sending BTC to an ltc1 address (or LTC to bc1) is a cross-chain mistake the format check should catch. If a UI ever accepts it, the coins are still gone. Double-check the network label.

Fees and Exchange

Fee estimation follows the Litecoin adapter (mempool-style). exchange.bridgeSoon includes Litecoin: no swap/bridge. Use Send/Receive only.

m/84'/2'/0'/0/0  →  ltc1… P2WPKH
RPC/history      →  litecoinspace.org Esplora API
Exchange         →  not available for LTC
Tip

The SegWit widget above is labeled with Bitcoin prefixes too — pick “bc1” vs “legacy” as an analogue, then use ltc1 in Receive. Related Bitcoin guide: SegWit vs legacy.

FAQ

Can I receive Litecoin on my Ethereum address? No. Different chain, different address. Enable Litecoin in the wallet (it is a fixed non-EVM net).

Why did an exchange reject ltc1? Some still want legacy. Ask for a bech32 invoice or send from a wallet that holds the format they require — do not convert the seed on a website.

Is MWEB supported? No. We do not claim MimbleWimble extension blocks. P2WPKH send/receive only.