TL;DR: According to the Zcash Foundation the fixes were merged for Zebra nodes that stopped syncing near the chain end. The October 21 update puts the work ahead of the stable NU7 release and reminds administrators of the old client’s deadline.
Zcash’s requirement for NU7 includes a smaller, but very important task: to keep nodes following the chain.
Inside A technical update was published on WednesdayThe Zcash Foundation described fixes for synchronization problems reported after Zebra 7.0.0-rc.0. His team confirmed the same issue on the main node.
The changes fix how Zebra requests blocks from peers and handles failed downloads. During the update, the work was merged into the development branch but did not appear in the production release. The platform described Zebra 7.0.0 as the next NU7 release.
Merger Code Should Always Be Available to Users
Delivery segmentation is important. The adjustment allowed to the development is not an exchange, a financial provider or an individual fund that is already in operation.
Managers usually get the benefit when a direct release is made and released. Services that rely on their own nodes must determine that those nodes are secure and keep track of the network.
The update features improvements to handling ZEC coins via Zebra’s RPC modes and a migration guide for services moving through the zcashd interface. These are embedded concerns that affect the integrity of the underlying systems even if they do not change the nature of the normal transaction.
A Practical Approach
The platform also announced that Zebra 6.4.xi builds will be completed on November 2, and that upgrading to release NU7 is an operational requirement for affected core users. The width NU7 planning thread which provides a round-the-clock update schedule.
The October 21 report covers engineering activities from October 6–19. It should be read as a statement of readiness, not as an indication that everything has been deployed across the network or that subsequent deployment decisions have been made.
There is also no basis in this update for describing the synchronization issue as money laundering. The reported problem is related to the node behavior and the actions necessary to release a stable client before the update.
