Zano Wallet Security
Honest framing on what the wallet protects, what the protocol protects, and what's on you.
What we mean by "security"
Wallet security has at least four distinct layers. We are explicit about each because the privacy-conscious audience punishes overpromising.
- Code integrity — the binary you run is the code we wrote, unmodified.
- Custody — only you control your private keys.
- Transaction privacy — the Zano blockchain hides amounts, addresses, and asset types.
- Network privacy — your IP and traffic patterns when the wallet talks to peers.
The first three are strong by default. The fourth is opt-in.
Layered privacy model
Chain-level privacy is strong by default. Every Zano transaction conceals amounts (Bulletproofs+), addresses (ring signatures + stealth addresses), and asset types (Confidential Assets). Enforced by protocol on every send and receive — there is no "private mode" toggle.
Network-level privacy is opt-in. Your IP is exposed to peers your wallet connects to (true of any P2P protocol). Run Zano over a VPN, Tor, or a trusted-peer list to add this layer.
What we publish with every release
- Full source code on the public repository
- Build instructions to reproduce binaries from source
- Versioned changelog and release notes
What we don't do
- No telemetry. The wallet does not phone home.
- No analytics in the desktop binary.
- No server-side key storage. Ever.
- No KYC, no email signup, no account.
- No third-party trackers in the app.
Antivirus false positives
Heuristic AV tools — Windows Defender most commonly — flag privacy-wallet binaries because they perform crypto operations and lack a Microsoft "reputation score." Confirm you downloaded directly from zanowallet.io, then add an exception in your antivirus settings if needed.
Network privacy options
Option A — VPN. Your IP exposed to the Zano network becomes your VPN provider's IP. Choose a provider you trust (or one that doesn't keep logs).
Option B — Tor. Configure your Zano daemon to use Tor's SOCKS5 proxy. Your IP exposed to peers becomes a Tor exit IP. Slower, more private.
Option C — Trusted-peer list. Edit zano.conf to specify add-priority-node directives that connect only to peers you run yourself or peers run by a community you trust.
What you're responsible for
- Protecting your seed phrase. Cold storage, multiple physical backups. Never in cloud docs, screenshots, email, or photos.
- Source of the build. Zano Wallet is distributed exclusively from zanowallet.io. Signature files are published alongside each release for verification.
- Operational privacy. Privacy is layered all the way down to your habits.
- Network privacy choices. Default chain privacy is strong; high-threat-model users add VPN, Tor, or trusted-peer config.
- Realistic expectations. "100% untraceable" doesn't exist. Privacy is a continuum.
Hardware Wallet Support
Zano Wallet does not currently support Ledger or Trezor. Hardware integration for Zano is on the Foundation's roadmap. We will update Zano Wallet to support hardware wallets when shipped. For now, your seed phrase is your hardware substitute.
You can replicate the discipline that makes hardware wallets useful with software:
- Cold-store the seed. Paper or metal. Keep offline.
- Use a dedicated device. Run Zano Wallet on a computer not used for general browsing.
- Backup hygiene. Multiple physical copies in geographically separate locations.
Frequently asked
Related
Get Zano Wallet for desktop
Open source. No signup. Full self-custody on Windows, macOS, and Linux.