TL;DR: The Zcash Basis says it merged fixes for Zebra nodes that stopped syncing close to the chain tip. The October 21 replace locations the work forward of a secure NU7 launch and reminds operators of the older shopper’s approaching cease date.
Zcash’s preparation for NU7 features a much less glamorous however important process: ensuring nodes hold following the chain reliably.
In an engineering replace revealed Wednesday, the Zcash Basis described fixes for synchronization issues reported after Zebra 7.0.0-rc.0. Its crew additionally confirmed the identical underlying trigger on a mainnet node.
The modifications alter how Zebra requests blocks from friends and handles failed downloads. On the time of the replace, the work was merged into the event department however had not appeared in a printed launch. The muse described Zebra 7.0.0 because the probably subsequent secure NU7 launch.
Merged Code Nonetheless Has To Attain Operators
That launch distinction issues. A repair being accepted into growth doesn’t imply an alternate, pockets supplier or particular person node is already working it.
Operators usually obtain the profit when an applicable launch is revealed and deployed. Providers counting on their very own nodes then want to determine that these nodes have caught up and proceed to observe the community appropriately.
The replace additionally describes enhancements to dealing with ZEC quantities via Zebra’s RPC varieties and a migration information for providers shifting from zcashd’s interface. These are integration issues that may have an effect on the reliability of downstream methods even when they don’t change what an strange transaction seems like.
An Approaching Operational Deadline
The muse repeated that Zebra 6.4.x is designed to cease round November 2, making an improve to the NU7 launch an operational requirement for affected mainnet customers. The broader NU7 planning thread supplies the encircling improve schedule.
The October 21 report covers engineering work from October 6–19. It ought to be learn as a dated account of readiness, not as proof that each merchandise was already deployed throughout the community or that each subsequent launch choice had been accomplished.
There’s additionally no foundation on this replace for describing the synchronization challenge as a theft of cash. The reported downside issues node conduct and the work wanted to ship a secure shopper forward of the improve.
