TL;DR: The Zcash Foundation says it merged fixes for Zebra nodes that stopped syncing near the chain tip. The October 21 update places the work ahead of a stable NU7 release and reminds operators of the older client’s approaching stop date.
Zcash’s preparation for NU7 includes a less glamorous but essential task: making sure nodes keep following the chain reliably.
In an engineering update published Wednesday, the Zcash Foundation described fixes for synchronization problems reported after Zebra 7.0.0-rc.0. Its team also confirmed the same underlying cause on a mainnet node.
The changes adjust how Zebra requests blocks from peers and handles failed downloads. At the time of the update, the work was merged into the development branch but had not appeared in a published release. The foundation described Zebra 7.0.0 as the likely next stable NU7 release.
Merged Code Still Has To Reach Operators
That release distinction matters. A fix being accepted into development does not mean an exchange, wallet provider or individual node is already running it.
Operators normally receive the benefit when an appropriate release is published and deployed. Services relying on their own nodes then need to establish that those nodes have caught up and continue to follow the network correctly.
The update also describes improvements to handling ZEC amounts through Zebra’s RPC types and a migration guide for services moving from zcashd’s interface. These are integration concerns that can affect the reliability of downstream systems even when they do not change what an ordinary transaction looks like.
An Approaching Operational Deadline
The foundation repeated that Zebra 6.4.x is designed to stop around November 2, making an upgrade to the NU7 release an operational requirement for affected mainnet users. The broader NU7 planning thread provides the surrounding upgrade schedule.
The October 21 report covers engineering work from October 6–19. It should be read as a dated account of readiness, not as proof that every item was already deployed across the network or that every subsequent release decision had been completed.
There is also no basis in this update for describing the synchronization issue as a theft of coins. The reported problem concerns node behavior and the work needed to deliver a stable client ahead of the upgrade.