Zcash Foundation offers Zebra Ándale alpha to speed up node operations

A prerelease aimed at operators

On October 31, 2026, Zcash Foundation presented Zebra Ándale, a performance-focused release of its Zcash node software. Numbered 7.1.0-alpha.0, it targets miners, pools, and the operators supplying their infrastructure. The official repository classifies it as a testing prerelease. It should therefore not be presented as a new stable version recommended indiscriminately to all users, or as a change already deployed across every node on the network.

The Foundation links the work to feedback from miners. A mining node must prepare work for mining machines, receive solved blocks, and relay new blocks to peers. Each stage has its own latency. Reducing the time needed to deliver new work is not the same measurement as accelerating cryptographic verification. That distinction matters when interpreting the announced results and avoiding application of a single multiplier to every node activity.

Less waiting rather than different rules

The documents describe replacing periodic waits with behavior that responds more directly to verified transactions and changes in the chain. They also describe changes in block-template preparation, relay, and recording results. The aim is to reduce delays and repeated work. The Foundation says validation rules are not relaxed: in its account, performance is not gained by accepting blocks that would previously have been invalid.

For prepared mixed blocks, the Foundation reports 17 milliseconds against 164 milliseconds with Zebra 7.0.0, a factor of 9.6 in that test. Those values belong to a specific measurement setup. They do not guarantee the same difference for operators using different hardware, workloads, or memory states. The live comparison dashboard also uses different conditions and should not be treated as automatically reproducing the prepared scenario.

Testing should preserve a way back

The release notes recommend testing the alpha on a node that can return to Zebra 7.0.0. They say the state format is retained, facilitating that return within the announced scope. Documentation for the development branch must also be distinguished from the stable-version guide: it can evolve with changes made after the prerelease. Operators therefore need instructions matching the exact version being tested, rather than mixing different software states.

The next step remains gathering feedback toward a stabilized release. The improvements concern infrastructure operation; they are neither a guarantee of mining revenue nor a prediction of ZEC’s price. Useful observations include measured timings, tool compatibility, and node stability under actual operating conditions. The announcement opens a documented testing effort without establishing that every installation will automatically achieve the same results.