Zcash Zakura Node Targets 50K TPS for Visa-Scale Privacy

Zcash just shipped the first piece of its most ambitious plan yet: a full node client called Zakura, built to handle 50,000 transactions per second while keeping every payment fully private. That is Visa and Mastercard territory — and the Zakura team calls it "the floor, not the target."

Released July 16 as version 1.0.0, Zakura arrives at a pivotal moment. The original zcashd client reached end of life on July 18. The Ironwood network upgrade (NU6.3) activates around July 28. And Zcash is still recovering from a near-fatal soundness bug discovered in May that left the Orchard shielded pool vulnerable for four years. Zakura is the software layer designed to carry the network through all of it.

What Is Zakura?

Zakura is a consensus-compatible Zcash full node written in Rust, forked from Zcash Foundation's Zebra codebase. It is maintained independently by Sean Bowe, a Zcash co-founder and the cryptographer behind Project Tachyon, and Dev Ojha, the Osmosis co-founder who now leads Valar Group. Both teams are funded by private ZEC donations rather than by any company or foundation.

The Zcash Foundation has publicly welcomed the fork. "Zebra was built to be forked," the Foundation wrote in a July 16 blog post. "Zakura's engineering is impressive — including faster initial sync, pruning, snapshot bootstrapping, and a compatibility path for zcashd operators — and it arrives at the moment the network needs more capable options, not fewer."

For operators running the legacy zcashd client, Zakura includes a compatibility mode that reproduces zcashd's interface, so wallets and exchange integrations built against the old client continue working without modification. Combined with pruned snapshots of roughly 11 gigabytes that bootstrap a fresh node in under two minutes — what the team calls "680 times faster" than syncing from genesis — Zakura dramatically lowers the barrier to running a full node.

The 50K TPS Roadmap: Tachyon, PIR, and Fast Blocks

The throughput target is not aspirational marketing. It is arithmetic. Mastercard and Visa process more than 50,000 transactions per second. Zcash's existing cryptography would require a node to ingest and verify over 500 megabytes of data every second to match that pace, because every shielded transaction carries a zero-knowledge proof, and proofs are large. The current stack cannot deliver anywhere near that.

Three parallel efforts are closing the gap:

First, Project Tachyon, led by Bowe, is developing recursive proofs — a technique where one proof attests to the validity of thousands of others. Instead of verifying thousands of individual proofs at consensus, a node verifies a single recursive proof. The team estimates this reduces the consensus data requirement from 500 MB/s to roughly 100 MB/s, a level they consider achievable with careful systems engineering.

Second, Valar Group is tackling the wallet bottleneck. Because Zcash hides who a transaction is for, a wallet cannot ask a server "which transactions are mine?" without revealing its identity. Instead, it downloads everything and tests each transaction locally, which caps wallet throughput at roughly one transaction per second. Valar's solution uses private information retrieval (PIR) — a cryptographic technique that lets a wallet fetch its own data from a server without the server learning which entries were requested. This would unbind wallet performance from chain throughput entirely.

Third, Zakura itself ships with an experimental block propagation system targeting sub-half-second delivery of new blocks to every node on the network. It is disabled by default for now, but it represents the networking layer required for high-volume proof verification and wallet traffic to be practical.

Ironwood: Fixing a Four-Year Vulnerability

The near-term test for all of this arrives with Ironwood (NU6.3), which activates on mainnet at block 3,428,143 — approximately July 28 at 8 a.m. Eastern. Ironwood introduces a new shielded pool, also called Ironwood, built on the same Orchard Action circuit and Halo 2 proof system but with one critical addition: a turnstile mechanism designed to contain any counterfeit ZEC that may have been minted through a four-year-old soundness bug.

In May 2026, Shielded Labs researcher Taylor Hornby discovered that the proof circuit for Orchard — Zcash's newest shielded pool, active since May 2022 — contained a flaw allowing an attacker to mint counterfeit ZEC with no onchain trace. Developers disabled Orchard through an emergency response, then restored it with a corrected circuit via the NU6.2 hard fork on June 3. But because zero-knowledge proofs reveal nothing beyond the fact that they verified, the chain holds no record of what any Orchard transaction moved, and nobody could prove counterfeit ZEC was never created.

Ironwood addresses this by capping what can leave the Orchard pool. ZEC amounts crossing into or out of shielded pools are public even when the transactions inside are not. By sealing Orchard to new deposits, the turnstile becomes the only exit. Honest balances can migrate out over time into the new Ironwood pool; counterfeit coins are trapped at the boundary. The Ironwood pool also introduces quantum-recoverable note plaintexts and is designed for formal verification from the start.

What This Means for Web3 Developers

For developers building privacy-preserving applications, Zcash's scaling roadmap offers a preview of what production-grade onchain privacy looks like. The combination of recursive proofs, PIR-based wallet infrastructure, and fast block propagation addresses the three bottlenecks — consensus verification, client scanning, and network latency — that have historically kept private blockchains at low throughput.

These techniques are not exclusive to Zcash. Recursive proof systems are increasingly relevant to Ethereum rollup architectures and zkEVM design. PIR has applications in any system where a client needs to query a server without revealing what it is looking for — from decentralized identity to confidential DeFi. The engineering patterns emerging from Zakura and Tachyon will inform privacy infrastructure across the broader web3 stack.

The Zcash Foundation has also made clear that its mission includes building cross-implementation conformance test suites and differential testing infrastructure — tooling that catches consensus divergences before they reach mainnet. For any team running critical blockchain infrastructure, this kind of verification layer is becoming essential.

If you are building privacy tools, payment infrastructure, or zero-knowledge applications, the underlying primitives — from proof recursion to shielded pools — are increasingly accessible through modern developer platforms. If you are ready to build, thirdweb offers developer plans that scale with your project, from hackathon prototypes to production-grade deployments.

The Road Ahead

Zakura 1.0.0 is the first live deliverable of a multi-year roadmap. The cryptography is still in development. The PIR solution is still research-stage. The fast block propagation system is experimental and off by default. But the pieces are now real, running software rather than whitepapers. And with Ironwood activating in less than two weeks, the network upgrade that tests the first of these ideas is imminent.

For a network that nearly broke four months ago, the pace of recovery is remarkable. Whether Zakura and its companion technologies can actually deliver Visa-scale privacy remains to be seen — but the blueprint is on the table, the code is shipping, and the clock is ticking toward July 28.