Skip to content

Litecoin wallet capabilities

Compare documented features, platform limits and the scope of actual tests. Every entry links to its evidence; unverified features stay unverified.

Documentation dates appear on each entry. Published experiments cover Core and Electrum-LTC; the separate recovery study also tests the Trust Wallet Core engine. Other entries remain documentation reviews. This is not a security ranking or a recommendation to install an old release.

Compare the recovery tests: distinguish restored addresses, discovered funds and signing authority. Read the new experiment report.

Reset

3 matching entries. Platform filters apply to the MWEB feature as well as the wallet. No affiliate tracking is attached to these documentation links.

Desktop full node

Litecoin Core

Documentation + published regtest experiments

Version scope: 0.21.5.8 · Checked 2026-09-24

MWEBDocumented
Coin controlAvailable through explicit transaction inputs; the GUI is not tested here
MultisigTested: legacy P2SH, 2-of-3, regtest
Recovery considerationsWallet-file backup. Multisig recovery also needs the script/policy and sufficient signing keys.

Published experiments cover eight 2-of-3 signing combinations and 14 checks of encrypted wallet-file recovery, receiving and spending across three standard address types. MWEB, mnemonic migration, GUI and hardware recovery are not tested.

Mobile and desktop software wallet

Cake Wallet

Documentation checked; no device test

Version scope: Documentation review; application build not pinned · Checked 2026-09-24

MWEBDocumented on iOS and Android only
Coin controlDocumented for Litecoin
MultisigNot verified for Litecoin in this review
Recovery considerationsDocumentation supports BIP39 and Electrum seed formats; record the selected format and any passphrase.

The Litecoin documentation explicitly excludes MWEB addresses and peg-in/out on desktop. A desktop Litecoin balance is not evidence of desktop MWEB support.

Mobile Litecoin wallet

Nexus Wallet

Documentation checked; no device test

Version scope: Documentation review; application build not pinned · Checked 2026-09-24

MWEBPrivate balance and ltcmweb1 addresses documented
Coin controlNot verified in this review
MultisigNot verified in this review
Recovery considerationsNew-wallet guidance describes a 24-word backup. Migration from Litewallet is a separate documented procedure.

The official help center distinguishes regular and private balances. Check the current app and both ends of the payment route; a standard receiving address is not a private MWEB address.

The published Core experiment

Executed on 2026-09-23 UTC using /LitecoinCore:0.21.5.8/ on an isolated regtest network. Eight candidate spends use the same test output. No mainnet funds were used; the candidate spends were checked with testmempoolaccept, not broadcast.

Signing keysComplete signatureAccepted by regtest mempool policy
noneNoNo
ANoNo
BNoNo
CNoNo
ABYesYes
ACYesYes
BCYesYes
ABCYesYes

Encrypted wallet recovery: receive, restore and spend

Executed 2026-09-24T08:43:24.191644+00:00 with /LitecoinCore:0.21.5.8/ on win32. Encrypted legacy wallet-file backup and recovery through Core RPC; three standard address types. No mainnet, device GUI, mnemonic, QR or MWEB interoperability test.

CheckResultEvidence and limits
Isolated regtestPassedNo external peer connections; freshly generated regtest chain.
Receive address: legacyPassedAddress is owned by the fresh receiver wallet.
Receive address: p2sh-segwitPassedAddress is owned by the fresh receiver wallet.
Receive address: bech32PassedAddress is owned by the fresh receiver wallet.
Three payments receivedPassedThree separate confirmed payments of 1 regtest LTC.
Balance restoredPassedLoaded an independent copy of the encrypted wallet backup on the same regtest chain.
Encryption preservedPassedRestored wallet is locked.
Ownership restored: legacyPassedBackup retains the receiving key and script.
Ownership restored: p2sh-segwitPassedBackup retains the receiving key and script.
Ownership restored: bech32PassedBackup retains the receiving key and script.
Spend after restore: legacyPassedSigned with restored wallet; regtest mempool policy accepted the candidate. Fixed 0.0001 LTC test fee; not a fee recommendation.
Spend after restore: p2sh-segwitPassedSigned with restored wallet; regtest mempool policy accepted the candidate. Fixed 0.0001 LTC test fee; not a fee recommendation.
Spend after restore: bech32PassedSigned with restored wallet; regtest mempool policy accepted the candidate. Fixed 0.0001 LTC test fee; not a fee recommendation.
Confirmed send after restorePassedOne restored-wallet candidate was broadcast and mined only on the isolated regtest chain.

QR generation is a separate website feature. An independent decoder recovered all three tested payment URIs exactly, including a Unicode reference. This does not establish that every wallet scans or honors every URI field. Mobile and hardware wallets still need device-specific tests.

Before choosing or migrating

Check the exact application build, platform and address type. A recovery test must match the actual backup format, passphrase and wallet policy. Never enter recovery words into this comparison page or a support message. For an unfamiliar feature, a documented capability is a starting point for a controlled test, not a guarantee of interoperability.

Payment request parsing evidence

We executed 20 identical URI cases at the parsing boundary of Electrum-LTC 4.2.2.1 and Cake Wallet v6.4.5. Duplicate amounts, precision and returned metadata differ. These are source-isolated function tests; they do not establish full application, scanner, device or signing behavior.

Frequently asked questions

What is the difference between documented features and tested behavior?
Documented entries reflect vendor release notes and manuals at the stated review date, whereas published tests record specific controlled experiments on pinned versions (such as Core 0.21.5.8 regtest multisig and recovery or Electrum-LTC 4.2.2.1 CLI checks).
Do all Litecoin wallets support optional MWEB privacy transfers?
No. MWEB support varies significantly by platform and software release; standard transparent LTC support on mobile or hardware wallets does not guarantee MWEB sending, receiving or seed-only recovery compatibility.
Is it safe to paste my recovery phrase into a compatibility checker?
Never enter seed phrases, private keys, wallet.dat files or passwords into any website or support chat. Verify backup formats and restoration procedures offline on controlled devices.
Jarosław Wasiński
Editor-in-chief · Financial markets and Litecoin education

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.

Background, selected work and editorial responsibility →

Founder of MyBank.pl Financial education and market analysis Named editorial responsibility