Polylog
The Polylog Crypto Intelligence Brief

Morning Edition · Monday, July 20, 2026Published at 1:27 AM EDT · New York

Zcash Ships Its First Client Built for Payment-Scale Private Transactions

The Zakura node targets 50,000 shielded transactions per second, and a July 28 hard fork will seal the older Orchard pool to contain a counterfeiting bug.

Zcash Ships Its First Client Built for Payment-Scale Private Transactions

Zcash, the oldest large privacy-focused blockchain, has released the first working piece of a plan to move from roughly one shielded transaction per second toward tens of thousands. The new Zakura client is designed to reach 50,000 private transactions per second, a rate the project compares to a card network, by reworking how the node validates zero-knowledge (ZK) proofs and stores shielded state.

The new client arrives with a defensive change. Zcash developers have scheduled a July 28 hard fork, named Ironwood, that will seal the older Orchard shielded pool after the discovery of a critical bug that could, in principle, allow counterfeit ZEC to be created inside the shielded set. Because balances in a shielded pool are hidden, developers cannot simply audit the supply. The fork instead uses the pool's turnstile, the accounting checkpoint that measures value entering and leaving shielded storage, to cap and contain any fraudulent coins as funds migrate to a newer pool.

The two events show the tension now shaping private chains. Confidential execution is being redefined from a niche feature into a requirement for serious on-chain use, a claim also made by newer entrants such as Miden, which argues that practical privacy, not optional privacy, is the condition for institutions to transact on public ledgers. Scaling that privacy without weakening it, and proving that a hidden money supply has not been corrupted, are the engineering problems that will decide whether the argument holds.

What this means

Privacy chains are competing on throughput and integrity at the same time, and both affect whether confidential settlement can host real payment volume. Zakura's target addresses capacity, while the Orchard bug shows the specific risk of shielded systems: because supply is hidden, a validation flaw can create invisible coins, and holders of ZEC are exposed until the turnstile fork closes that gap. The parties that gain are privacy protocols that can demonstrate both scale and auditable soundness, and the parties that lose are those whose confidentiality claims cannot be independently checked.

What to watch

  • Whether the Ironwood fork activates cleanly on July 28 and the migration off Orchard completes without disputed balances, which would confirm the counterfeiting risk is contained.
  • Independent benchmarks of Zakura's real-world throughput against the 50,000-per-second target, since sustained shielded performance, not a lab figure, is what would attract institutional interest.
  • Whether other privacy networks respond with their own scaling or compliance-visibility features, signaling the contest over who sets the privacy standard is widening.

Observations to monitor, not financial advice.

3 sources

Synthesized from: CoinDesk · crypto.news · Miden

Part of a tracked trend

Privacy Chains Pivot From Niche to Institutional Pitch

Over 3-6 months, confidential execution reframes as a prerequisite for serious/institutional on-chain use, with privacy L2s shipping live networks and contesting who controls confidentiality.