Zcash activates NU7 on testnet, setting up an Oct. 20 mainnet decision
The upgrade targets 25-second blocks and disables v4 transactions, which could strand Sprout-held ZEC if not moved before activation.
Zcash’s NU7 network upgrade activated on testnet at block 4,465,026 on Oct. 4 at 18:21:45 UTC, starting a live testing window ahead of a targeted Nov. 5 mainnet rollout. The key catalyst now is an Oct. 20 developer go/no-go decision that will either lock in a mainnet activation height or push the timeline back.
NU7 Goes Live on Zcash Testnet, Starting the Clock to Oct. 20
NU7 is now running on Zcash’s public testnet after the network hit its scheduled activation point at testnet block 4,465,026, mined on Oct. 4 at 18:21:45 UTC, per the ZecBlock testnet explorer. Zcash also confirmed via an X post that NU7 was live on testnet, moving the upgrade from “planned” to “operationally testable” for node operators, wallet teams, and exchanges.
The testnet flip matters less as a headline than as a clock-start for coordination. NU7 changes consensus rules and transaction handling, so the ecosystem’s job over the next few weeks is to run the release candidate in conditions that resemble production, then feed back what breaks before developers commit to a mainnet activation height.
The protocol changes being exercised are trader-relevant because they alter network behavior, not just code hygiene. NU7 targets a reduction in Zcash’s block spacing from 75 seconds to 25 seconds, a structural shift that should compress confirmation cadence if it holds under real-world testnet variance. NU7 also adds a Network Sustainability Mechanism that redirects part of transaction fees into future block rewards, though the portion and formula are not specified in the material describing the testnet activation.
The Zcash Foundation’s guidance to testnet operators was explicit: run the NU7 release candidate “under real conditions.” That is a signal that the project wants operational feedback, not just green unit tests, and it raises the odds that any edge-case incompatibility gets surfaced before the Oct. 20 decision gate.
Sprout and v4 Transaction Shutdown: The Compatibility Risk Traders Can’t Ignore
NU7 disables version 4 transactions, and the stated consequence is unusually concrete: ZEC held in Zcash’s legacy Sprout shielded pool would become unspendable unless users move those funds before NU7 fully activates. That is not a theoretical “some wallets may need updates” warning. It is a compatibility cutoff that creates a user-action deadline.
Mechanically, this is the kind of upgrade detail that tends to surface as last-minute friction across the stack. Wallets and custodians need to ensure they are not generating or accepting a transaction format the network will reject post-activation, and they need a clean operational path for any users still sitting in Sprout. If that migration path is unclear, or if messaging lands late, the failure mode is predictable: rushed moves near the activation window, support tickets, and temporary deposit and withdrawal policy changes by venues that do not want to be the last hop holding unspendable funds.
For traders, the immediate risk is not “NU7 breaks Zcash,” it is that the v4 shutdown and Sprout spendability constraint can create uneven readiness across counterparties. The market impact, if any, typically comes from operational bottlenecks, not from the existence of an upgrade on a test network.
Decision Gate: What Would Confirm a Nov. 5 Mainnet Activation
The next hard milestone is Oct. 20, when Zcash developers are scheduled to make a final decision on whether to proceed with mainnet activation and to set the activation height based on testnet experience. A published activation height is the practical confirmation traders can anchor to. A delay announcement, or a decision that punts height-setting, is the cleanest signal that the Nov. 5 target is slipping.
Two other items sit in the “watch for clarity” bucket during the test window. First, whether documentation is updated to specify the Network Sustainability Mechanism’s fee-redirection parameters, since “part of transaction fees” is directionally clear but not modelable without a portion or formula. Second, ecosystem readiness signals, including whether operators follow the Zcash Foundation’s instruction to run the NU7 release candidate under real conditions, and whether wallets and exchanges begin publishing concrete guidance on v4 disablement and Sprout fund migration as Nov. 5 approaches.
My Read: This Upgrade Is Less About Hype and More About Operational Footguns
The testnet activation is being treated like the event, but the threshold that matters is Oct. 20, because that is when developers either commit to a mainnet activation height or implicitly admit the test window found something that needs more time. Until that decision lands, “Nov. 5” is a target date, not a locked schedule.
What stands out is how non-negotiable the v4 shutdown is framed for Sprout funds. If the ecosystem does not get ahead of that messaging, the setup starts to look like a familiar operational squeeze where the chain upgrade is fine, but the user migration and venue policies become the real volatility vector. This development matters in practical terms if Oct. 20 produces a firm activation height and the ecosystem publishes clear Sprout migration and transaction-compatibility guidance early enough to avoid a last-minute scramble.
