Zcash Wallet Release Notes

Key Facts

• Zingo 2.0.20 was published on June 5, 2026 and its notes say it adopted zingolib v4.0.0 for NU6.2 alongside bug fixes.
• YWallet 1.15.3 was published on June 4, 2026 with a fix for NU6.2 circuit-version detection through the zcash-sync update.
• Zkool 6.23.0 was published on July 2, 2026 with account/database UX work and downloadable Sapling parameter handling.
• The Zkool repository describes the project as YWallet's successor, but that statement does not prove that every account, platform, or backup path migrates automatically.
• A public release tag proves that a project published a version. It does not measure wallet security, current compatibility for an individual account, privacy quality, or whether an update is safe to apply without reading the official instructions.

This edition's maintenance read

The important wallet story is not that one app has a newer-looking version number. It is that the three reviewed projects are in different maintenance situations. Zingo published a release tied to NU6.2 support. YWallet published a focused compatibility fix while the project is openly framed as transitioning toward Zkool. Zkool then published its own release with setup, account, and parameter-management changes. That is enough evidence to tell a user where to look. It is not enough evidence to tell every user what to install.

Release notes are operational evidence. They tell you what a project says changed, when it published the change, and where the official artifacts live. They do not expose your account state, establish that a device is safe, or replace a recovery plan. House of Zcash keeps those limits visible because wallet update pages get dangerous when they sound like an instruction to move funds immediately.

Zingo 2.0.20: a current NU6.2 maintenance signal

Zingo's published 2.0.20 release is dated June 5, 2026. The release notes say that the wallet adopted zingolib v4.0.0 for Network Upgrade 6.2 and included bug fixes. That makes the release relevant to a user checking whether the project had a public NU6.2-era update. It does not justify inventing a list of fixes that the release note does not contain.

For a Zingo user, the practical question is narrower: which official mobile channel and version is actually installed, and does the update path match the app's own instructions? Zingo remains a self-custody light-client design, which means keys and transaction detection remain on the client while the selected lightwallet server can still observe an IP address and block-level activity patterns. A new version does not erase that network-metadata boundary.

The safe habit is to begin from the official repository or authenticated store listing, read the associated notes, and confirm recovery material is under your control before changing devices or app state. Never hand recovery words to a website, a person in a direct message, or a fake update prompt.

YWallet 1.15.3: maintenance inside a transition

YWallet 1.15.3 is dated June 4, 2026. Its public notes identify a specific fix: updating the zcash-sync submodule to correct NU6.2 circuit-version detection. That is a concrete compatibility repair, not a broad declaration that every future workflow should stay on YWallet forever.

The transition context matters. YWallet still lists packaged installation routes across Android, iOS, Windows, Linux, and macOS, while the newer Zkool repository describes itself as YWallet's successor. Both facts can be true at once. A project can remain distributed and usable while new feature work and long-term attention gather around a successor.

That does not mean a user should export or migrate blindly. Wallet accounts, seed formats, address types, encrypted databases, hardware-signing arrangements, and platform support can differ. The correct next step is the project's documented migration or recovery path for the actual wallet version in use, followed by a small test if value must move. The radar intentionally refuses to turn a repository description into a universal conversion promise.

Zkool 6.23.0: successor work with setup consequences

Zkool's 6.23.0 release is dated July 2, 2026. The visible notes include database-manager account-list work, downloadable Sapling parameters, parameter-directory fixes on Android and iOS, and several maintenance or usability changes. Those details matter because setup changes are not cosmetic for a wallet. Parameter handling, storage locations, and account navigation can affect what a user needs to understand before updating or starting fresh.

The release also reinforces why a successor label is not a recommendation engine. Zkool's current project scope includes advanced controls that may suit experienced users, while a user with an established YWallet configuration may care more about platform availability, backup compatibility, or a documented migration path. The source supports a released version and declared successor relationship. It does not support a blanket claim that Zkool is automatically the best choice for every Zcash holder.

For a new setup, start at the project-controlled source, verify the platform and dependencies you actually need, and make a recovery plan before funds arrive. For an existing setup, preserve the old recovery path until the replacement is confirmed. That is boring advice because it is the advice that survives when a release note is less simple than a marketing headline.

What a release record can and cannot prove

A release tag can prove that a repository published a named version at a stated time. A project repository can describe a successor relationship. An official installation page can show the platform paths a project currently lists. Those are useful, reviewable facts. They are the facts in the Wallet Maintenance Radar.

They cannot prove that a wallet is secure, that it has no undiscovered bug, that its current build supports every receiver or account format, or that an update will preserve every local state. They also cannot certify the privacy of a payment. Shielded transaction privacy depends on the route a wallet constructs, the pool and receiver involved, wallet behavior, network metadata, counterparties, and any voluntary disclosure. A release age is not a privacy score.

That boundary matters for search readers as much as for users. A page promising the best or safest wallet from three public releases would be fake precision. A page that shows the release evidence, names the transition, and links the reader to the actual wallet capability and backup guides is more useful and easier to verify.

A safer update sequence

First, identify the exact wallet and version you already use. A logo or a seed phrase label is not enough. Confirm the official project page and the release notes for that precise app. Second, make sure recovery material is available offline and that you understand what it restores. Recovery data should never enter a browser form, cloud note, or support chat.

Third, read the project's official instructions for the operating system and any transition you are considering. If the update changes a device, receiver path, database, or account structure, test the recovery or transfer path with a small amount before treating the full balance as portable. Fourth, verify the result in the wallet that can actually decrypt and spend the shielded funds. A public explorer cannot confirm the encrypted recipient, amount, or memo of a fully shielded payment.

The radar is deliberately a reading and verification aid. It does not connect to a wallet, calculate whether an account is migratable, or ask for an address, key, seed, balance, or transaction history.

Methodology and review contract

The build-time source pipeline reads public GitHub repository and release metadata for the projects included in the site's reviewed ecosystem snapshot. This edition uses the source window reviewed on July 18, 2026 and displays Zingo 2.0.20, YWallet 1.15.3, and Zkool 6.23.0 exactly as the validated snapshot records them. Direct release pages and the corresponding GitHub API release endpoints remain linked so the record can be checked without trusting the interface alone.

The three lenses answer different questions from the same records. Current Signals isolates public releases from Zingo and Zkool. Transition Watch keeps YWallet and Zkool together so the successor relationship does not get lost. Release Ledger shows every record and its boundary. The full three-row evidence table remains in the page markup regardless of interaction state.

This article carries a 30-day review window. A new release, altered project direction, or broken official source requires a new editorial check instead of silently changing the meaning of the current edition.

FAQ