Zcash just shipped faster private-payments software. The security test starts now.
Zakura gives Zcash a real scaling path, but the market already learned what one private-money bug can cost.
CryptoVibe Desk · zcash · privacy · infrastructure
- →Zakura v1.0.0 launched Wednesday as a pruned, fast-syncing Zcash node built from the Zebra client.
- →The bigger plan targets 50,000 private transactions per second, but today's shipped piece is sync and node performance.
- →Watch Ironwood on July 28, because its withdrawal cap is the live test after June's soundness bug.
- full node → A full node checks the chain for itself instead of trusting another server.
- shielded transaction → A shielded transaction hides sender, receiver, or amount while still proving the payment is valid.
- zk-SNARK → A zk-SNARK is a proof that lets someone verify a claim without seeing the private data behind it.
- soundness bug → A soundness bug means the proof system may accept something false as valid.
Zakura v1.0.0 shipped Wednesday. It is a new Zcash full node maintained by cryptographer Sean Bowe and Valar Group's Dev Ojha. The node forks Zebra, the Zcash Foundation client, and adds pruned fast sync. It also includes compatibility mode for zcashd, the legacy client that hit end of life on July 18.
The bet is simple: Zcash can scale private payments only if its plumbing gets smaller, faster, and safer. Zakura handles the first two pieces for now. It makes Zcash easier to run before proving Zcash can handle payment-scale private usage.
CoinDesk reports a pruned snapshot size of about 11 GB and an initial sync under two minutes. The announcement claims that is 680 times faster than full chain sync. That is useful, but it is not 50,000 private payments per second.
The larger plan has three parts. Zakura is the node path. Project Tachyon is the proof path, using recursive zero-knowledge proofs. Valar's private information retrieval work tackles the wallet problem.
That wallet problem matters for privacy. Wallets need to find their own payments without exposing what they are looking for. If you're holding ZEC, this split matters. A fast node is not the same as 50,000 private payments on mainnet.
Current shielded throughput is still messy. CoinDesk puts it around one private transaction per second, while Crypto Briefing cites 3 to 20. NU7 testnet work reportedly cut block times from 75 seconds to 25 seconds after its May 22 launch. It also doubled shielded TPS, but that is still testnet.
The security context is the only number that matters. Crypto Briefing says ZEC fell about 48% after June's critical vulnerability. Ironwood, also called NU6.3, activates July 28. It introduces a turnstile on the Orchard shielded pool, which holds about 30% of ZEC supply as of July 19.
The turnstile caps Orchard withdrawals to contain any counterfeit ZEC from the long-running soundness bug. That is not marketing. That is blast-radius engineering. The tradeoff is slower exits for a tighter bound on damage.
Zcash finally has a credible scaling map. Zakura handles node sync. Tachyon targets proof compression. PIR tackles wallet privacy. But after June, throughput milestones only count if they ship without another proof failure.
Bowe and Valar's choice to ship Zakura first is defensible because faster node sync is useful now. Still, the Zcash story only gets credible if Ironwood contains Orchard withdrawals without breaking normal user exits.
By August 15, watch whether Ironwood activates on July 28 without emergency patches and whether Orchard withdrawals stay capped as designed.
Primary links and supporting reads used by the desk for this story.
Forward this.
