Lite Wallet review 2026 — what we shipped and what's next
REVIEW · 2026-04-20
Lite Wallet review 2026 — shipped features and roadmap
A product self-review of v3.16.0: the full feature set, honest limitations, and the roadmap for the next six months. Written by the team, for users who want the unvarnished picture.
Lite Wallet is a non-custodial Litecoin wallet available on Windows, macOS, Linux, iOS, and Android. The current release is v3.16.0, dated 2026-04-20. This review is written by the Lite Wallet team as a product self-assessment: what shipped in v3.16.0, what works well, what has known limitations, and what is on the roadmap for the next two quarters. It is not a marketing page. It is closer to a changelog with context — a plain description of the product's current state, intended for users deciding whether the wallet fits their needs.
What shipped in v3.16.0
Five-platform unified release: Windows (.exe installer), macOS (.dmg, Apple-signed), Linux (.zip portable), iOS (App Store), Android (Google Play). Every platform on the same version, the same release day. MWEB (Mimblewimble Extension Block) confidential transactions on every platform — the peg-in and peg-out flow is identical across desktop and mobile. LitVM support — LTC-20 tokens and smart contract interactions from inside the wallet, signed with the same 12-word paper key, gas paid in LTC. Ledger and Trezor hardware wallet integration on all desktop platforms, with on-device signing for standard Litecoin transactions. Tor routing for SPV connections (Settings → Privacy → Route over Tor). Atomic swap module for trust-minimised LTC↔BTC exchanges. CSV transaction export including MWEB-peg events. Redesigned UI with dark mode by default, accessible contrast, and keyboard navigation.
Where Lite Wallet is strong
Platform coverage is the clearest win. Several competing Litecoin wallets implement MWEB on one platform but not another — desktop without mobile, Android without iOS. v3.16.0 ships the same MWEB implementation on all five. Second, LitVM is native rather than bolted on: tokens appear alongside LTC in the same balance view, there is no separate dapp browser to install, and gas payment is handled automatically in LTC. Third, the hardware wallet flow is first-class: Ledger and Trezor support is in the main wallet build, not a separate 'hardware edition'. Fourth, the download experience is designed for verification — signed binaries a public GitHub repository, and MIT-licensed source.
Known limitations in v3.16.0
Hardware wallet signing for MWEB transactions is not yet supported. Ledger and Trezor sign standard Litecoin transactions on-device in v3.16.0, but MWEB peg-in and peg-out flows still require desktop signing. Hardware wallet signing for LitVM transactions is also on the roadmap rather than in this release. On mobile, hardware wallet pairing over USB-C or Bluetooth is not yet available — mobile users who want cold-key signing should use the watch-only xpub import flow and co-sign from the desktop client. The Linux build is a portable .zip rather than a packaged .deb or .rpm — users who want system package integration will need to create their own wrapper for now.
Roadmap
Hardware signing for MWEB
Ledger and Trezor MWEB peg-in/peg-out signing with on-device verification of blinded amounts.
Hardware signing for LitVM
On-device signing for LTC-20 transfers and LitVM contract calls with human-readable transaction previews.
Mobile hardware wallet pairing
USB-C and Bluetooth pairing flows for iOS and Android, starting with Ledger Nano X.
Linux packaging
.deb and .rpm packages with signed repository metadata for Debian, Ubuntu, Fedora.
Additional platforms
Browser extension and command-line interface under evaluation. No commitment date yet.
How this product is developed
Lite Wallet is open source under the MIT License. The code is in a public GitHub repository; issues and pull requests are visible to anyone. The team publishes signed release binaries with Code signing on /security so users can verify that the file on their disk matches the one built from the public source tree. The wallet is non-custodial by design — there is no server that holds user keys, no account to create, no data to collect. See /about for the full picture of how the product is built and maintained.