Skip to content

Wallets

Last reviewed: 2026-05-11

The right Zcash wallet depends on what you want to do with it. This lesson covers the four wallets most people end up using, what each is optimized for, and what to check before picking one.

The single most important variable: does the wallet support Orchard shielded transactions? A wallet without Orchard support can still participate in Zcash, but you won’t get the strongest privacy or be in the same anonymity set as modern users.

WalletPlatformBuilt byOrchardNotable
Zashi → ZodliOS / AndroidZODL (the ex-ECC wallet team)YesShielded by default; renamed Zashi → “Zodl: Zcash Wallet” in Jan 2026
YwalletiOS / Android / DesktopHanh Huynh-HuuYesMulti-pool, power-user features
NighthawkiOS / AndroidNighthawkAppsYesShielded-first, simpler UI
Zecwallet LiteDesktop / iOSCommunitySapling-only (legacy)Long-standing, lighter on features

Wallet support evolves; double-check Orchard status on the wallet’s own site before picking. The Zcash Foundation’s wallet page is one source of truth.

This is the wallet to start with. One naming wrinkle to get out of the way first:

Whatever the store calls it this month, it is:

  • Shielded by default. Receiving uses a Unified Address; the wallet prefers Orchard.
  • Mobile-only: optimized for everyday flows like sending, receiving, and viewing memos.
  • Open source. Repos historically lived under the Electric-Coin-Company GitHub org and may have moved post-restructure; the canonical install is the App Store / Google Play listing for “Zodl: Zcash Wallet”.
  • Light-client based. Sync is fast on modern phones thanks to ZIP-307 light-wallet protocols.

If you’re new and want one wallet to start with, Zashi/Zodl is the easy pick. The 60-second walkthrough uses it.

Ywallet supports the broadest set of Zcash features:

  • All three live pools (transparent, Sapling, Orchard).
  • Multi-account, multi-device.
  • Shielded → shielded conversions, pool migrations, transparent shielding.
  • Hardware-wallet integration on some platforms.
  • Advanced features like crosschain functionality.

Trade-offs: more features mean more UI surface and more ways to accidentally reduce your privacy if you don’t read carefully. If you’re running multiple accounts, hardware-backed keys, or specific shielded operations, this is the wallet that will let you do them.

Nighthawk is a community-built shielded-by-default wallet for mobile. It targets the same use case as Zashi (everyday shielded payments) with a different UI and an independent codebase. Some users prefer it for its visual style or its particular feature mix.

Both Zashi and Nighthawk are shielded-first. Picking between them is mostly a preference call.

Zecwallet Lite: long-standing desktop option

Section titled “Zecwallet Lite: long-standing desktop option”

Zecwallet Lite was historically the go-to desktop wallet. Active development has slowed and it has not shipped Orchard support; it remains useful for legacy Sapling flows but shouldn’t be the wallet of choice for new users today. Treat it as a transitional tool if you have older wallet state to recover.

Before you commit funds to a wallet, look for:

  1. Open-source code with a public repo. Privacy software you can’t audit is privacy software you have to trust.
  2. Active maintenance: recent commits, recent releases, response to issues. Stale wallets are a security risk.
  3. Orchard support if you care about strongest privacy + future- proofing.
  4. A clear backup story. Most Zcash wallets use a 24-word seed phrase compatible with ZIP-32. Read the backup instructions and test recovery on a second device before funding.
  5. A view-key story if you’ll do accounting, audits, or any selective-disclosure use case (see Selective Disclosure).

Hardware support for Zcash shielded operations is limited. Trezor and Ledger have historically supported transparent ZEC; shielded support has trailed because the proving overhead is high for embedded devices.

There’s ongoing work, for example Zcash Foundation’s hardware-wallet research, but as of this writing, treat shielded hardware-wallet integration as emerging rather than mature. Mobile wallets with strong device-based key storage are the practical alternative.

Custodial wallets (exchanges, brokerages) hold ZEC on your behalf. They tend to support transparent ZEC only and require you to deshield to withdraw. Treat them as bridges to fiat, not as your primary wallet for holding or transacting.

If your goal is shielded money, your money should live in a self-custody shielded wallet. Anything else compromises the property you came for.

A practical first-run sequence:

  1. Install a wallet from its official site (verify the URL, typo-squat wallets exist).
  2. Generate a new seed and write it down on paper: not in a password manager you don’t fully trust.
  3. Verify recovery on a second device before funding.
  4. Generate a Unified Address. Share it as your default.
  5. Receive a tiny amount first. Confirm the balance shows up shielded.
  6. Then move larger amounts.

The next lesson walks through your first shielded transaction in more detail.