← All insights
RELEASEZcash Forum · ZcashFoundation

Zebra 6.4.0 adds a light client server

It added an experimental lightwalletd-compatible gRPC server and lowered the default ZIP 317 fee, but a critical bug was later found, and 6.4.0 and 6.4.1 were recalled.

Zebra 6.4.0 is a release that includes security fixes along with an experimental lightwalletd-compatible gRPC server, a lower default ZIP 317 fee, and precomputed block templates for miners. 6.4.1, released the same day, fixed an issue where sync could stall near the chain tip. However, an update notice at the top of the post says that both 6.4.0 and 6.4.1 have been recalled and should not be run. A high-severity bug let one peer halt a node with a single message, and 6.4.2 fixes it.

There are three security advisories. A forged block body with a legitimate hash could cancel a sync round, letting a malicious peer repeatedly delay sync (GHSA-3c94-hf7p-g5mf); this was fixed so the body is now requested again from other peers. A problem where peers that altered the coinbase scriptSig on the inbound path were not penalized was also fixed. Connection limits and bans now apply per IPv6 /64 subnet. Bans expire after 24 hours instead of lasting until restart, and peers that announce blocks containing duplicate transactions also lose score.

As a new feature, setting rpc.lightwalletd_listen_addr turns on an experimental gRPC server that implements the lightwalletd CompactTxStreamer interface, directly supporting light clients. Following zcash/zips#1352, the mempool accepts at least 1,000 zatoshis per ZIP 317 logical action (previously 5,000), and the minimum transaction is 2,000 zatoshis. It caches Orchard, Ironwood and Sapling bundle verification results, and when a miner address is set it precomputes the block template so getblocktemplate responds immediately.

With NU7 tentatively scheduled for November 5, the end-of-support halt period was cut from 15 to 12 weeks, so 6.4.x halts around November 2. The author said this shortening is not ideal and that there is no plan to make it routine. Nodes can check the exact halt height with the getdeprecationinfo RPC. In addition, equal-work chain selection now prefers the first-received tip, and the zcashd-compat sidecar's reorg limit was raised from 99 to 1,000 blocks.

The recommendation is as follows. The original post said to upgrade directly to 6.4.1 and prepare for the NU7-supporting release due the following week, but now 6.4.0 and 6.4.1 must not be used and you must upgrade to 6.4.2 immediately. Versions 6.3.0 and earlier are not affected. 6.4.2 includes all changes from the two recalled releases. Library users should note that there are API changes in zebra-rpc and zebra-state that break compatibility.

This summary is based on the original; check the original for exact details.