Lite Wallet supports routing its SPV peer connections through the Tor network. When Tor routing is enabled, Litecoin peers see a Tor exit node's IP instead of your device's IP. This adds a network-layer privacy complement to MWEB's on-chain privacy. Combined, MWEB hides transaction amounts and addresses on-chain while Tor hides your IP from the network of Litecoin peers that could otherwise cluster your wallet activity by source IP.

Why Tor matters

Every Litecoin wallet connects to peers to learn the current chain state, send transactions, and receive incoming transaction notifications. Without Tor, those peers see your device's public IP. A motivated observer running many peer nodes can cluster wallets by source IP — correlating multiple addresses back to a single user. This is a well-documented surveillance technique on Bitcoin and similar chains. Tor routing breaks the link. Peers see a Tor exit-node IP, which rotates across many users and has no connection to your device. MWEB adds the on-chain layer: amounts hidden, addresses unlinkable. Together, the two features give end-to-end privacy that neither provides alone.

How it works in Lite Wallet

Settings → Privacy → Tor routing: toggle on. Lite Wallet starts a local Tor client (bundled, no separate install) and routes all peer connections through it. Sync times are slightly slower over Tor — typically 20-50% longer than direct connections — due to Tor's relay hops. That's the tradeoff for network-layer privacy. On iOS and Android, Tor routing uses iCepa/Orbot integration where supported; the mobile Tor bundle is lighter than desktop. On Linux and macOS, users who run their own system Tor service can point Lite Wallet at their local SOCKS proxy instead of the bundled client.