What to Know

  • Zakura has launched at version 1.0.0 as a new Zcash full node maintained independently of the Zcash Foundation.
  • The client is a pruned, fast-syncing fork of Zebra, the Zcash Foundation's node software, and includes compatibility for legacy zcashd integrations.
  • The original zcashd client reaches end of life on July 18, making compatibility important for wallets and exchanges that still rely on its interface.
  • Zakura is part of a wider Zcash scaling effort alongside Project Tachyon and private information retrieval research.
  • Market participants involved in the rebuild want Zcash to approach payment-network scale, with Visa and Mastercard cited as handling more than 50,000 transactions per second.
  • The team says existing Zcash cryptography would require more than 500 MB/s of node throughput at that volume.
  • Zakura supports the Ironwood upgrade, formally NU6.3, which activates on July 28 at block 3,428,143, roughly 8 a.m. Eastern.
  • Ironwood introduces a turnstile mechanism designed to limit withdrawals from the Orchard shielded pool after a long-standing soundness bug raised concerns over possible counterfeit ZEC.

Zakura Arrives as a New Zcash Infrastructure Layer

Zakura has entered the Zcash ecosystem as a new full node client built for faster synchronization, lower storage demands, and continuity for applications still tied to the network's older software stack. Released at version 1.0.0, the client is maintained by Sean Bowe, a founding member of Zcash's zero-knowledge cryptography, and Dev Ojha, the Osmosis cofounder who now leads Valar Group. Their teams are funded by private ZEC donations, rather than by a company or a foundation.

The launch matters because full nodes are the backbone of a blockchain network. A full node keeps a complete copy of the ledger and independently checks transactions against the network's consensus rules. In Zcash, that means verifying whether blocks and transactions follow the shared rulebook that determines what the network accepts as valid. If a node enforces a different rule set, it no longer follows the same chain as the rest of the network.

Zakura is a fork of Zebra, meaning it began from the Zcash Foundation's node software and was rebuilt from that base. The new client is not simply a cosmetic alternative. It is being positioned as one operational pillar in a larger attempt to move Zcash from a network constrained by private-transaction performance toward a system that can support far higher transaction volume while preserving privacy and verifiability.

Fast Syncing and Pruning Aim to Reduce Node Friction

One of Zakura's most immediate features is pruning. In blockchain infrastructure, pruning refers to deleting older data that a node no longer needs to operate safely. That can reduce disk usage substantially, making node operation less burdensome for users, developers, wallets, and infrastructure providers.

The Zakura team publishes ready-made pruned chain snapshots of about 11 gigabytes, with old data stripped out. A new node can download that prepared copy instead of pulling the full history block by block from peers. The result is a dramatically faster setup process. The team says a node can go from nothing to running in under two minutes, a process described as 680 times faster.

That kind of faster bootstrapping can be important for resilience. If it is easier and quicker to operate a node, more participants may be able to run infrastructure, recover from outages, test applications, and support the network without needing to wait through a long initial synchronization cycle. For privacy-focused chains, robust independent verification is especially important because users rely on the network's rules to preserve both monetary integrity and transaction confidentiality.

Compatibility With zcashd Eases the Transition

Zakura also includes a compatibility mode that reproduces the interface of zcashd, the original Zcash client. That is significant because zcashd reaches end of life on July 18. Wallets, exchanges, and other integrations built against zcashd may need time to migrate, and a compatible interface can reduce disruption by allowing existing systems to keep working as they adapt.

For exchanges and wallet providers, infrastructure changes can be operationally sensitive. A node client is not just backend software; it can affect deposits, withdrawals, balance tracking, and transaction broadcasting. By maintaining compatibility with legacy interfaces, Zakura gives service providers a bridge between the older Zcash stack and newer infrastructure without forcing every integration to be rewritten immediately.

The Scaling Ambition Centers on Payment-Network Throughput

The broader ambition behind Zakura is far larger than node convenience. Zcash builders are aiming at a future where private payments can operate at global payment-network scale. Mastercard and Visa are cited as handling more than 50,000 transactions per second, and that level is described by the team as a floor rather than a final target.

The challenge is that Zcash privacy depends on cryptography that carries computational and data costs. Private transactions include proofs, and those proofs must be checked. At payment-network volume, the team says Zcash's existing cryptography would require more than 500 MB/s of throughput from a node. That burden is far beyond what current Zcash software is described as being able to sustain.

This is the arithmetic driving the infrastructure push. If private transactions are to scale without sacrificing verification, the network needs to shrink the amount of data that nodes must process and reduce the workload that wallets must carry. Zakura addresses the node layer, but it is only one part of the plan.

Project Tachyon Targets the Proof Bottleneck

Project Tachyon, led by Bowe, is aimed at the cryptographic side of the scaling problem. Its focus is recursive proofs, a technique in which one proof can attest to the validity of many other proofs. In practical terms, that would allow a node to verify a single proof rather than checking thousands individually.

The purpose is to reduce the amount of consensus data the network must handle. The team says Tachyon could reduce the requirement for consensus data from 100 megabytes per second to 500 megabytes, a level they claim can be reached with careful engineering. The phrasing underscores that the goal remains a technical development path rather than a completed production reality.

Recursive proof systems are increasingly important in crypto infrastructure because they can compress verification work. For Zcash, the stakes are particularly high. The network's value proposition is not simply transaction throughput but private transaction throughput with verifiability. Scaling one without preserving the other would not meet the design goal.

Wallet Performance Is a Separate Privacy Challenge

Wallets face a different bottleneck. Because Zcash hides the recipient of a private transaction, a wallet cannot simply ask a server which transactions belong to it without compromising privacy. If a wallet makes that request directly, it risks revealing what it is trying to find.

The current approach requires wallets to pull down data and test entries locally, which is why wallet software is described as topping out at about one transaction per second. That ceiling creates a major obstacle for any attempt to support large-scale private payments. Even if nodes become faster, users still need wallets capable of finding and processing their own transactions efficiently.

Valar Group is working on private information retrieval techniques to address that issue. Private information retrieval would allow a wallet to fetch its own data from a server without the server learning which entries were requested. If successful, that would remove a critical wallet-side bottleneck while maintaining the privacy assumptions that make shielded transactions useful.

Fast Block Propagation Adds Another Piece

Zakura also includes work on fast block propagation, which means broadcasting newly mined blocks across the network as quickly as possible. For a high-volume chain, fast propagation is essential. If blocks move too slowly between nodes, the network can face inefficiencies, stale data, and delays that undermine the benefits of faster proofs and better wallets.

The client ships with an experimental system aimed at delivering every block to every node in under half a second. That system is switched off by default for now, indicating that the feature is not yet being treated as standard production behavior. Still, its inclusion shows that the scaling effort is not limited to proof size or wallet lookup. Network communication itself must also improve if Zcash is to approach the scale being discussed.

Ironwood Becomes the Near-Term Test

The most immediate milestone is Ironwood, formally known as NU6.3. The upgrade activates on mainnet at block 3,428,143, roughly 8 a.m. Eastern on July 28, and Zakura supports it from release. Bowe said on July 10 that all major organizations are committed to that height, which is a week later than originally planned after exchanges and wallet providers requested preparation time.

Ironwood is not only a routine upgrade. It is the network's response to a serious issue involving Orchard, the newest Zcash shielded pool. Shielded pools are the private side of the network, where transaction amounts and participants are hidden and zero-knowledge proofs provide evidence that the rules were followed without revealing the underlying details.

Orchard Bug Raised Supply Integrity Concerns

On May 29, Shielded Labs researcher Taylor Hornby found that the proof circuit for Orchard contained a soundness bug. The flaw could have allowed an attacker to mint counterfeit ZEC without leaving an onchain trace. The issue had been live since Orchard activated in May 2022.

Developers disabled Orchard through an emergency response completed on June 2. They then restored it with a corrected circuit through the NU6.2 hard fork at block 3,364,600 on June 3. That fix addressed the circuit problem going forward, but it could not prove what happened while the bug existed.

The difficulty comes from the same privacy design that makes Zcash distinctive. A zero-knowledge proof reveals nothing beyond the fact that it verified. As a result, the chain does not show what any Orchard transaction moved, and nobody can prove that counterfeit ZEC was never created during the period when the flaw was live.

Ironwood's Turnstile Is Designed to Contain Risk

Ironwood introduces a turnstile mechanism at the boundary of the Orchard pool. The mechanism caps what can leave and what can enter by relying on a feature of Zcash's shielded design: amounts crossing into or out of shielded pools are public, even when activity inside the pools remains private.

By sealing Orchard to new deposits and making the turnstile the only exit, the upgrade aims to prevent any possible fake coins inside the pool from fully entering circulating supply. Honest balances can migrate out over time, while excess supply may be trapped at the boundary. The goal is to restore confidence in the token's supply reliability without exposing private transaction details.

For Zcash, the moment is both technical and reputational. Zakura points toward a more scalable future for private payments, while Ironwood addresses a concrete integrity challenge from the network's recent past. Together, they show an ecosystem trying to modernize its infrastructure, preserve privacy, and strengthen monetary assurances under close scrutiny from users, exchanges, wallets, and technical traders.

Frequently Asked Questions (FAQs)

What is Zakura?

Zakura is a new Zcash full node client released at version 1.0.0. It is a fork of Zebra, supports pruning and fast synchronization, and is maintained independently of the Zcash Foundation.

Why is Zakura important for Zcash?

Zakura is important because it lowers infrastructure friction and supports the broader effort to scale Zcash private payments. It helps nodes sync faster, reduces storage demands, and provides compatibility for systems built around zcashd.

What happens to zcashd?

The original zcashd client reaches end of life on July 18. Zakura includes a compatibility mode designed to reproduce the zcashd interface so wallets and exchange integrations can continue operating while the ecosystem transitions.

What throughput goal are Zcash builders discussing?

Zcash builders are discussing payment-network scale, with Visa and Mastercard cited as handling more than 50,000 transactions per second. The team describes that level as a floor for its long-term ambition.

What is Project Tachyon?

Project Tachyon is a cryptographic scaling effort focused on recursive proofs. The idea is for one proof to verify the validity of thousands of others, reducing the amount of data nodes must check at consensus.

Why are Zcash wallets a bottleneck?

Zcash wallets cannot simply ask a server which private transactions belong to them without risking privacy leakage. Because they need to pull down and test data, wallet software is described as topping out at about one transaction per second.

What is Ironwood?

Ironwood, formally NU6.3, is a Zcash upgrade scheduled to activate on July 28 at block 3,428,143. It introduces a turnstile mechanism for the Orchard shielded pool and is supported by Zakura from release.

Why was Ironwood needed?

Ironwood was developed after a soundness bug was found in the Orchard proof circuit. The flaw may have allowed counterfeit ZEC to be created without an onchain trace, though the privacy design means nobody can prove whether that happened.

How does the turnstile mechanism work?

The turnstile caps what can leave and enter the Orchard shielded pool by using public information at the pool boundary. It is designed to let honest balances migrate out over time while preventing possible counterfeit coins from fully entering circulating supply.

Photo by Alesia Kozik on Pexels