Gemini Moves Zcash Infrastructure to Zakura Ahead of NU7

Gemini has migrated its Zcash infrastructure from Zebra to Zakura, an open-source full node built to handle faster synchronization and recovery as the network prepares for its NU7 upgrade. The exchange says its production deployments reached the Zcash chain tip in just over six hours with Zakura, compared with close to one day using Zebra. The move is intended to prepare Gemini’s backend infrastructure for a planned threefold increase in block frequency without changing how customers deposit or withdraw ZEC.

According to Gemini’s official announcement, Zakura is a consensus-compatible fork of Zebra written in Rust and designed around faster synchronization, pruning and recovery. Gemini’s migration changes the node software supporting its Zcash operations rather than modifying the Zcash protocol itself. The exchange’s payout systems continue using the same Zcash-style RPC interface, keeping the infrastructure change behind the scenes for customers.

Zakura Cuts the Cost of Node Recovery

Zakura’s own published benchmarks put a full blockchain synchronization at roughly four hours and 20 minutes, versus almost 21 hours for Zebra under the benchmark conditions. Gemini’s production experience was slower than Zakura’s benchmark but still materially faster than its previous setup. The two figures should not be treated as identical tests because Gemini’s six-hour result comes from its own deployment environment rather than Zakura’s benchmark configuration.

The software also supports pruned snapshots of roughly 12 GB, which Gemini says can bootstrap a node about 680 times faster than a conventional peer-to-peer synchronization. That matters operationally when infrastructure needs to be rebuilt after an outage or failure. Reducing recovery time becomes more valuable as NU7 increases the number of blocks a node must process over a given period. Similar client-readiness work is occurring elsewhere, including Geth releases preparing Ethereum testnets for upcoming network upgrades.

Zakura emerged this year as part of a changing Zcash development landscape. The implementation was forked from Zebra and reached its initial release in July, while separate teams have continued funding protocol and privacy infrastructure after Zcash developers raised more than $25 million for new development work. Gemini’s deployment provides a production use case for Zakura, but it does not mean Zebra has been replaced across the wider Zcash network.

NU7 Targets 25-Second Zcash Blocks

NU7 is designed to reduce Zcash’s target block spacing from 75 seconds to 25 seconds, meaning compatible nodes will need to process roughly three times as many blocks over the same interval. ZIP 218 also introduces global and per-pool action limits intended to contain validation and shielded-sync costs as block frequency rises. The faster schedule is a consensus change, not simply a performance setting that Gemini activates by installing Zakura.

The current ecosystem timeline targets testnet activation for October 6 and mainnet for November 5. However, the deployment specification still lists the activation heights as TBD, with the mainnet height scheduled to be assigned on October 20. That makes November 5 the current target rather than an immutable activation point today. The distinction mirrors other upgrade cycles where software readiness precedes final network activation.

Gemini has not yet published production benchmarks showing Zakura operating under NU7’s 25-second mainnet block schedule. The next concrete milestone is therefore NU7 testnet activation, followed by assignment of the mainnet activation height and evidence that exchange infrastructure remains stable under the faster consensus rules. Until then, Gemini’s six-hour synchronization result demonstrates improved current-state recovery performance, not yet performance under the post-NU7 workload.