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.
5 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 + a limited regtest experiment
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. |
The downloadable test covers eight signing-key combinations. It does not test MWEB, GUI recovery or production custody. A full node needs its own storage and synchronization.
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.
Desktop software wallet
Electrum-LTC
Documentation checked; no application test
Version scope: 4.2.2.1 listed on the project website (5 June 2022) · Checked 2026-09-24
| MWEB | Not verified in the cited documentation |
|---|---|
| Coin control | Address freezing documented; full input-selection workflow not tested |
| Multisig | Not verified in this review |
| Recovery considerations | Electrum-LTC seed and wallet file. Imported keys can require a separate backup. |
The project identifies itself as a community-maintained Electrum port. The cited download page is old; its listed version is not a security recommendation. Check the project and signed release before installation.
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.
Hardware wallet with companion software
Trezor + Trezor Suite
Documentation checked; no hardware test
Version scope: Documentation review; device, firmware and Suite build not pinned · Checked 2026-09-24
| MWEB | Not verified for Litecoin in this review |
|---|---|
| Coin control | Litecoin-specific workflow not verified |
| Multisig | Litecoin-specific workflow not verified |
| Recovery considerations | Device and backup format matter; follow the instructions for the exact model and backup type. |
Trezor lists native Litecoin support in Suite. That alone does not establish support for MWEB or every advanced Litecoin feature. The documented litecoin: URI handler is desktop-only.
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 |
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.