Zebra 6.4.0 and 6.4.1 security releases
An experimental lightwalletd-compatible gRPC server was added and ZIP 317 fees were lowered. End-of-support was also moved earlier to prepare for NU7, and upgrading directly to 6.4.1 is recommended.
The Zcash Foundation announced the Zebra 6.4.0 and 6.4.1 releases. 6.4.0 is a security release that adds an experimental lightwalletd-compatible gRPC server, lowers the default ZIP 317 fee, and speeds up block template delivery for miners. 6.4.1, released the same day, fixed an issue where sync could stall near the chain tip. Node operators were strongly advised to upgrade directly to 6.4.1.
There are three security advisories. A problem where forged block bodies could halt sync (GHSA-3c94-hf7p-g5mf) was fixed so the body is now requested again from other peers. A problem where peers relaying blocks with a rewritten coinbase scriptSig were not penalized (GHSA-4f6v-mj46-gxg3) was also fixed. Peer-count limits and bans now apply per IPv6 /64 range (GHSA-jhpp-8h75-7pv5). Bans expire after 24 hours, and peers that announce blocks containing duplicate transactions also lose score.
The most notable change is the end-of-support policy. The end-of-support period was shortened from 15 weeks to 12 weeks, so 6.4.x halts around November 2, ahead of the planned NU7 activation date of November 5. The Zebra team said it does not intend this to become common practice, and operators can check the exact halt height with the getdeprecationinfo RPC. rpc.max_response_body_size now has an upper limit of 4,294,967,295 bytes, and larger values are rejected when the configuration loads.
New features include a lightwalletd CompactTxStreamer-compatible gRPC server enabled with rpc.lightwalletd_listen_addr. Following zcash/zips#1352, the mempool lowered the minimum fee per ZIP 317 logical action from 5,000 to 1,000 zatoshi and raised the fee-weighted ratio limit from 4 to 10. When a mining address is set, block templates are precomputed, and caches for Orchard, Ironwood and Sapling verification results plus pool value metrics were introduced.
Bug fixes include sync stalling permanently after a restart (6.4.1), repeated restarts on transient timeouts, the chain selection rule for equal-work chains (the first-received tip wins), mempool peer slot release, and z_gettreestate consistency during a reorg. The zcashd-compat sidecar's reorg limit was raised from 99 to 1,000 blocks. A release supporting NU7 is scheduled for next week, and 6.4.1 is available from GitHub, crates.io and Docker Hub.
This summary is based on the original; check the original for exact details.