ZODL announced on October 22, 2026 that support for the original Zcash Android and Swift Wallet SDKs will end when NU7 activates. Wallet users should ask for their application’s actual upgrade plan. Do not confuse SDK version 4.0.0, a wallet’s own version number and transaction format v4: those labels describe different objects.
What the maintainer’s support announcement says
The ZODL notice names 4.0.0 as the final planned original-SDK release and expects NU7 on November 5. It says previously released MIT-licensed code remains available, while ongoing development moves to the ZODL SDKs under AGPL-3.0-only. The expected day is not an exact activation time or a statement about every wallet’s readiness.
For a user, the useful next record is a statement from the maintainer of the app actually installed. For a developer, it is an inventory of the dependencies and services that app uses. A library support cutoff does not tell a reader which build has been distributed to a phone, or whether the application team independently maintains the relevant code.
The other v4 is a consensus-format question
The current NU7 deployment document, ZIP 259, is marked Proposed and specifies mainnet activation height 3,543,405. It states that transaction format v4 becomes invalid at activation and that funds left in Sprout would become unspendable under those rules. That is a material legacy-funds question, not something to dismiss as only a change in SDK maintenance.
Do not infer the transaction format from a similar software version number. If you may have legacy Sprout funds, obtain the wallet maintainer’s documented preparation path before the proposed activation. This article does not identify the pools holding a reader’s funds or establish that a particular wallet can migrate them. Avoid an unverified recovery tool offered in response to the upgrade news.
| Version or milestone | What it describes | What to ask the maintainer |
|---|---|---|
| Original SDK 4.0.0 | A planned software-library release | Which dependency and maintenance plan does the app use? |
| Your installed wallet build | The application on your device | Which official build and backend are prepared for NU7? |
| Transaction format v4 | A consensus-level transaction format | Does any legacy-funds preparation apply to this wallet? |
| NU7 activation | The network-upgrade boundary | What current schedule and readiness evidence support the plan? |
A useful wallet notice names the application, not only the SDK
The original Android and Swift repositories are separate from the successor ZODL Android and Swift projects linked by the maintainer. Use those identities to understand a developer’s statement. Do not treat a repository name as a compatible consumer-app download.
An illustrative support request can be short: identify the app, installed build and official distribution source, then ask which release and backend support the upgrade and whether any legacy-funds preparation is needed. A reply that only repeats NU7 supported is less useful than one identifying the relevant build and instructions. Keep the reply with the announcement so a later update can be compared with it.
- Identify your actual wallet application, installed build and official update source.
- Read its maintainer’s NU7 readiness statement rather than assuming every app uses the same SDK.
- Ask explicitly about any legacy Sprout preparation if that may apply to your funds.
- Follow the wallet’s documented update and backup procedure; do not send a recovery phrase to support or an upgrade website.
- Recheck the network schedule and the application’s current instructions before the activation boundary.
What developers need to resolve separately
Choose and document a maintenance path, then review the licensing terms appropriate to the dependencies incorporated into the app. Compatibility testing, distribution and support communication remain separate jobs. A decision about source-code maintenance is not proof that the release reached users, and this article does not determine a particular company’s licence obligations.
For a separate exchange, review supported coins and networks, the order workflow, and the receiving instructions in the simple-swap form. An SDK or NU7 announcement does not establish acceptance of every address type or legacy pool by KOT.CASH. Confirm the actual route without exposing the wallet’s recovery material.
FAQ
Does the Zcash NU7 upgrade date give an exact SDK-support cutoff time?
The notice ties the support cutoff to activation and gives an expected calendar day. Recheck the current deployment information rather than treating the day as a fixed timestamp.
What should a Zcash Android wallet user ask before updating?
Ask which official app build and backend are prepared, and whether legacy-funds preparation applies. Do not send a recovery phrase as part of that support request.
What belongs in a Zcash NU7 developer timeline?
Separate dependency maintenance, compatibility work, app distribution and user communication. A library version number is not the same thing as a transaction-format version.