The Zcash NU7 upgrade has a block-height deadline, not a guaranteed clock time. Mainnet node operators need compatible software before block 3,543,405, which the Zcash Foundation expects around November 5. Its November 3 engineering update puts the final preparations in focus as activation approaches.
For Zebra operators, the stable release to check is Zebra 7.0.0. It supports NU7 and bundles seven security fixes. This is not a newly announced emergency release: version 7.0.0 was published on October 22. The immediate news is the approaching network transition and what operators must verify beforehand.
The deadline is the block, not November 5 at midnight
The Foundation’s stable-release announcement says all mainnet node operators must upgrade before height 3,543,405 to stay on the consensus chain. After activation, upgraded nodes disconnect older peers, while incompatible nodes can follow a different chain. November 5 is an estimated date; actual block production determines when the change takes effect.
That warning primarily concerns node, exchange, mining and infrastructure operators. It does not mean every person holding ZEC needs to install a full node. Wallet users should check their provider’s NU7 compatibility guidance rather than assume an exchange balance or wallet app requires the same steps as Zebra.
What the seven Zebra fixes address
The release groups five high-severity and two medium-severity advisories. At a high level, they concern stalled synchronization, excessive verification work, a process crash and incorrect treatment of peers. Independent coverage on November 3 also distinguishes the older security fixes from the imminent upgrade deadline.
These disclosures should not be described as a reported theft. One checkpoint-synchronization advisory explicitly says its impact was availability: no invalid block reached disk, no chain fork occurred and funds were unaffected. That finding is specific to the advisory, not a blanket promise about every operational risk during NU7.
Database, wallet and release checks matter too
Zebra 7.0.0 migrates stored state from database format v28 to v29 on first startup. The official release notes advise backing up the state/v28 directory beforehand. Zebra 6.x cannot read the new format, so moving back to it after migration requires a full resynchronization. Operators also need to review breaking configuration, RPC and monitoring changes.
A separate protocol warning deserves attention: the Foundation says version-4 transactions become invalid after activation. Because Sprout transfers only use that version, funds left in the Sprout pool become unspendable. This is a documented network transition, not one of the seven security bugs. Affected users and service operators should consult the official release guidance and their wallet provider before activation.
The newer Zebra 7.1.0-alpha.0, branded Ándale, is an experimental miner-focused build. It should not be confused with the stable 7.0.0 recommendation. Seeder operators have a separate task: the engineering update calls for Zeeder 1.8.0 before activation.
Does NU7 mean faster ZEC issuance?
No. NU7 reduces target block spacing from 75 seconds to 25 seconds, but adjusts rewards so scheduled issuance per day remains unchanged. The Foundation says the four-year halving schedule and 21 million ZEC cap are preserved. ZIP 218 does not recommend reducing confirmation counts simply because blocks arrive more frequently.
The practical checkpoint is therefore software and service readiness before the activation height—not a price prediction, a promise of instant finality or an assumption that an estimated date is a fixed deadline.
