Privacy starts
on your device.

Choose your infrastructure and manage what you share across decentralized networks. Local routing and supported Tor connections help limit exposure.

Explore privacy

ZEUS WALLETPrivacy demo

Route inspector

Interactive demo

Your device

ZEUS WalletLocal routing

Peer 1Forwards its hopPeer 2Forwards its hopDestinationReceives payment

Local routing: Route calculation uses network information on your machine. The payment path is calculated locally.

●Calculated on your device●Forwarded through peers

Local calculation

Routes are calculated on your device.

Limited peer visibility

Forwarding peers see the information needed for their hop.

Public blockchain

On-chain transactions remain on Bitcoin’s public ledger.

Understand privacy limits+

Know who
sees what.

Understand the boundaries of Bitcoin and Lightning privacy. See what the network, forwarding peers and service providers may learn.

Visibility and limits

Explore each layer

Bitcoin networkOn-chain activity is public.

Lightning peersForwarding peers see their hop.

Service providersYour setup determines what is shared.

Invoice wrapping and LSPs
The payer need not learn your node’s public key. The wrapping provider knows your node so it can forward the payment.

Privacy depends on your connections and the services you use. These controls help manage exposure; they cannot remove Bitcoin’s public record or make payments anonymous. Wallet configuration is managed locally; some modes use remote infrastructure for synchronization or encrypted channel-state storage.

Tor is a trademark of The Tor Project. This project is not sponsored by The Tor Project.