YWallet

Key Facts

• The official installation matrix lists YWallet 1.15.3 for Android, iOS, Windows, Linux, and macOS.
• YWallet supports Transparent, Sapling, and Orchard receivers, plus Unified Addresses that can contain all three.
• Version 1.15.3 was published on June 4, 2026 with a fix related to NU6.2 circuit-version detection.
• The Microsoft Store package was discontinued because of that store's self-custody wallet policy; other official packages remain listed.
• The Zkool repository calls Zkool the successor to YWallet, so new users should compare both before choosing a long-term setup.

YWallet's current status

YWallet is not a dead download page. Its official installation matrix still lists a current version, direct platform routes, and packaged builds for five operating-system families. The 1.15.3 release was published on June 4, 2026 and addressed NU6.2 circuit-version detection. That is a concrete maintenance signal, not a vague claim that the project is active.

The awkward part is succession. The same developer now describes Zkool as the successor to YWallet. In practice, YWallet sits in a transition period: it still has broad distribution and familiar workflows, while the newer project is where more ambitious account, signing, Tor, and PCZT work is concentrated. Existing YWallet users do not need to panic. New users do need to compare the two paths instead of treating the older name as the automatic choice.

Platform coverage is YWallet's clearest advantage

Few self-custody Zcash wallets publish such a wide set of packaged builds. The official matrix points to Android through Google Play or a standalone APK, iOS through the App Store, Windows as a portable ZIP, Linux as AppImage, Flatpak, or Flathub, and macOS as a universal DMG. That breadth matters for people who want the same wallet family on a phone and a conventional desktop.

Download origin still matters more than convenience. Wallet binaries control keys and transaction signing, so an unofficial mirror is not an interchangeable substitute. Start from ywallet.app or the project's GitHub release, verify that the platform and version match, and avoid search ads or third-party APK sites. The Microsoft Store listing is specifically marked discontinued because of a store policy change; that statement does not mean every Windows build or the entire wallet was discontinued.

Transparent, Sapling, Orchard, and Unified Addresses

YWallet gives users more visibility into Zcash receiver types than many simplified mobile wallets. Its documentation lists Transparent, Sapling, and Orchard addresses and explains that a Unified Address can contain receivers for all three pools. The wallet derives distinct keys for those pools from the same seed, so the backup may recover the account while each receiver still has different privacy properties.

That control is useful only when the user understands it. A transparent receiver exposes transaction details on the public chain. Sapling and Orchard use shielded protocols, but they are not the same pool and wallet support can differ. A Unified Address is a container for receivers; it is not a guarantee that every counterparty will choose the shielded receiver. Check the actual send flow, especially when moving funds to an exchange or service with limited receiver support.

Who YWallet fits

YWallet is strongest for experienced users who want desktop availability, direct pool controls, and a wallet that does not hide Zcash's address model. It can also make sense for an existing user who already has a tested backup and knows the application's recovery process. Those are real advantages, particularly when mobile-only interfaces feel too constrained.

It is a weaker default for someone who wants the simplest possible first wallet. More control creates more decisions, and the successor transition adds another one. Zodl or Zingo may be easier mobile starting points, while Zkool deserves attention from power users who specifically want its newer multi-account and signing work. There is no honest universal winner; the relevant question is which maintenance path and privacy workflow you are prepared to verify.

Backup and recovery before migration

A successor announcement is not permission to improvise with recovery material. Before changing wallet software, confirm that the current YWallet installation opens correctly, identify the account and receiver types in use, and verify the seed backup offline. Never paste a seed phrase into a website, a support chat, or a form that claims to check compatibility.

If you decide to test Zkool or another maintained wallet, use official documentation and start with a small amount or a controlled restore on a clean device. Wallet recovery can depend on birthday height, derivation behavior, and which pools held funds. Keep the old installation intact until balances and transaction history have been checked. A migration is complete when the funds and recovery path are verified, not when a new app merely accepts the words.

FAQ