Zcash ships Zakura node as zcashd sunsets ahead of July 28 Ironwood upgrade
The new client fast-syncs from 11 GB snapshots and supports the NU6.3 ‘turnstile’ aimed at containing potential counterfeit ZEC risk.
Zcash ecosystem developers released Zakura v1.0.0, a new full node designed to reduce sync time and ease migrations as the legacy zcashd client reached end-of-life on July 18. The launch lands days before the July 28 Ironwood (NU6.3) upgrade, which adds a protocol-level ‘turnstile’ to cap Orchard shielded pool withdrawals after a discovered soundness bug.
Key Takeaways
- Zakura v1.0.0 is live as a new Zcash full node maintained independently of the Zcash Foundation by Sean Bowe and Dev Ojha, funded by private ZEC donations.
- The software is a pruned, fast-syncing fork of Zebra and ships a zcashd-compatibility mode as zcashd reached end-of-life on July 18.
- Operators can bootstrap from pruned chain snapshots of about 11 GB, with the team claiming a fresh node can be running in under two minutes, “680 times faster.”
- Ironwood (NU6.3) is scheduled for July 28 at block 3,428,143 (~8 a.m. ET) and introduces an Orchard ‘turnstile’ to contain potential counterfeit ZEC tied to an Orchard soundness bug.
Zakura v1.0.0 Lands as zcashd Hits End-of-Life
Zcash’s infrastructure stack is being forced through a client transition window. Zakura v1.0.0 shipped as a new full node implementation at the same time zcashd, the original Zcash client, reached end-of-life on July 18.
Operationally, that timing matters more than the throughput marketing. Full nodes enforce consensus rules, and exchanges, wallets, and market makers need predictable node behavior around upgrade windows. Zakura is positioned as a drop-in path for teams that historically integrated against zcashd, with a compatibility mode designed to reproduce the zcashd interface so existing integrations can keep working without rewrites.
Zakura is maintained independently of the Zcash Foundation by Sean Bowe and Dev Ojha, and it is funded by private ZEC donations rather than a company or foundation. That independence cuts both ways for operators: it can speed iteration, but it also shifts due diligence onto integrators who need to be comfortable running a new production client.
Fast Sync by Snapshot: What Zakura Changes for Node Ops
Zakura is a fork of Zebra, meaning it started from the Foundation’s node codebase and was rebuilt from there. The key operational change is its snapshot-driven fast sync model, enabled by pruning.
Pruning deletes older blockchain data a node no longer needs to validate the current chain. With old data stripped, the team distributes ready-made pruned chain snapshots of about 11 GB. A new node can download the snapshot instead of syncing the full chain block-by-block from genesis, and the team claims that takes a node from zero to running in under two minutes, “680 times faster.”
If that workflow holds up under real-world conditions, it reduces the cost of standing up redundant nodes and rotating infrastructure. That matters most when uptime is non-negotiable, like hard-fork windows where exchanges and wallets want quick recovery paths if a node fails or a deployment needs to be rolled back.
Zakura also ships with an experimental fast block propagation system aimed at delivering every block to every node in under half a second. It is switched off by default.
Ironwood on July 28: The Turnstile Supply-Integrity Patch
The near-term catalyst is not theoretical scaling. It is Ironwood (NU6.3), scheduled to activate July 28 at block 3,428,143 (roughly 8 a.m. Eastern). The upgrade introduces a ‘turnstile’ mechanism to cap withdrawals from the Orchard shielded pool.
Ironwood exists because of an Orchard proof-circuit soundness bug discovered May 29 by Shielded Labs researcher Taylor Hornby. The flaw had been live since Orchard activated in May 2022 and could have allowed an attacker to mint counterfeit ZEC with no on-chain trace. Developers disabled Orchard through an emergency response completed June 2, then restored it with a corrected circuit via the NU6.2 hard fork at block 3,364,600 on June 3.
The problem is the gap between “fixed going forward” and “provably safe historically.” Zero-knowledge proofs reveal only that a proof verified, not what value moved inside Orchard, so the chain cannot prove counterfeit ZEC was never created during the multi-year window. Ironwood’s turnstile is designed to contain that uncertainty by controlling what can cross the Orchard boundary, using the fact that amounts entering and exiting shielded pools are public even if internal transfers are private.
Catalyst Checklist Into July 28: Client Migrations and Upgrade Readiness
The threshold events are clear and close together. First is the post–July 18 reality: whether major infrastructure providers publicly migrate to Zakura (or other clients) and whether zcashd-compatibility mode works cleanly in production without edge-case breaks.
Second is July 28 itself. The market will care less about the activation headline and more about confirmations from major exchanges and wallets that they have upgraded and resumed normal deposit and withdrawal policies.
There is also parameter risk. Any updates from core teams on the Orchard turnstile settings and operational guidance for moving funds across the Orchard boundary after activation will shape how quickly users can migrate balances out over time.
Finally, Zakura’s performance claims need independent validation. Third-party benchmarking of the 11 GB snapshot flow and the under-two-minute startup claim would turn a good demo into something operators can underwrite.
Why ZEC’s Near-Term Narrative Is Infrastructure Risk, Not TPS Dreams
I’m treating this as an infrastructure and supply-integrity story with a hard date, not a scaling breakthrough. The July 28 Ironwood activation is a concrete catalyst because it is explicitly designed to contain potential counterfeit ZEC risk that cannot be audited on-chain due to how zero-knowledge proofs work.
The threshold that matters is whether the client migration and the turnstile rollout land cleanly across exchanges and wallets. If that plumbing holds, the setup starts to look structural rather than narrative-driven, because it reduces upgrade-window fragility and narrows the supply-integrity overhang into a defined mechanism traders can reason about.
