Litecoin.watch · Research & practical tools
Litecoin wallet capabilities
Compare documented features, platform limits and the scope of actual tests. Every entry links to its evidence; unverified features stay unverified.
Compare the recovery tests: distinguish restored addresses, discovered funds and signing authority. Read the new experiment report.
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
| MWEB | Documented |
|---|---|
| Coin control | Available through explicit transaction inputs; the GUI is not tested here |
| Multisig | Tested: legacy P2SH, 2-of-3, regtest |
| Recovery considerations | Wallet-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
| MWEB | Documented on iOS and Android only |
|---|---|
| Coin control | Documented for Litecoin |
| Multisig | Not verified for Litecoin in this review |
| Recovery considerations | Documentation 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
| MWEB | Private balance and ltcmweb1 addresses documented |
|---|---|
| Coin control | Not verified in this review |
| Multisig | Not verified in this review |
| Recovery considerations | New-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 keys | Complete signature | Accepted by regtest mempool policy |
|---|---|---|
| none | No | No |
| A | No | No |
| B | No | No |
| C | No | No |
| AB | Yes | Yes |
| AC | Yes | Yes |
| BC | Yes | Yes |
| ABC | Yes | Yes |
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.
| Check | Result | Evidence and limits |
|---|---|---|
| Isolated regtest | Passed | No external peer connections; freshly generated regtest chain. |
| Receive address: legacy | Passed | Address is owned by the fresh receiver wallet. |
| Receive address: p2sh-segwit | Passed | Address is owned by the fresh receiver wallet. |
| Receive address: bech32 | Passed | Address is owned by the fresh receiver wallet. |
| Three payments received | Passed | Three separate confirmed payments of 1 regtest LTC. |
| Balance restored | Passed | Loaded an independent copy of the encrypted wallet backup on the same regtest chain. |
| Encryption preserved | Passed | Restored wallet is locked. |
| Ownership restored: legacy | Passed | Backup retains the receiving key and script. |
| Ownership restored: p2sh-segwit | Passed | Backup retains the receiving key and script. |
| Ownership restored: bech32 | Passed | Backup retains the receiving key and script. |
| Spend after restore: legacy | Passed | Signed with restored wallet; regtest mempool policy accepted the candidate. Fixed 0.0001 LTC test fee; not a fee recommendation. |
| Spend after restore: p2sh-segwit | Passed | Signed with restored wallet; regtest mempool policy accepted the candidate. Fixed 0.0001 LTC test fee; not a fee recommendation. |
| Spend after restore: bech32 | Passed | Signed with restored wallet; regtest mempool policy accepted the candidate. Fixed 0.0001 LTC test fee; not a fee recommendation. |
| Confirmed send after restore | Passed | One 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.