Zakura Slashes Zcash Private Tx Time to Under 200ms

Zakura released an open-source cryptography toolkit on Aug. 29 that dramatically reduces the time required to construct shielded Zcash transactions. The new library, Zakura Common v1.3.0, replaces several cryptographic components used by wallets and full nodes and — according to developer benchmarks — can cut local proof construction from more than three seconds to below 200 milliseconds in some tests.

Key performance gains and what they mean for Zcash users

Zakura Common targets the heavy computational work involved in shielded transactions: zero-knowledge proof generation, Sinsemilla hashing, trial decryption during wallet scan, and zk-SNARK verification on nodes. The project’s benchmark summary highlights several headline improvements that are likely to improve the responsiveness of shielded wallets and reduce verification load on full nodes:

Major benchmark highlights

• Proof construction: mobile proof generation improved more than 14x; desktop proof generation increased by over 5x.
• Transaction construction: in some developer tests, end-to-end local construction dropped from >3 seconds to under 200 ms (developer benchmark — not a guaranteed on-device time).
• Sinsemilla hashing: speedups exceeded 21x, reducing the cost of cryptographic commitments used by shielded transactions.
• Proof verification: zk-SNARK verification on nodes improved roughly 4x–8x, lowering validation cost and potentially speeding transaction propagation.
• Trial decryption: wallet scanning performance improved by more than 1.5x in tests.

How Zakura Common integrates with wallets and nodes

One of Zakura Common’s most important design choices is that it is a non-consensus library. Wallet and node developers can integrate the libraries without changing Zcash consensus rules, which means adoption does not require a hard fork, coordinated network upgrade, or simultaneous activation across node operators. Zakura released the code under dual MIT and Apache 2.0 licenses so teams can use, audit, modify, and redistribute the libraries freely, subject to those license terms.

Early adopters and developer rollout

Zakura itself has adopted the stack in version 1.3.0, and Vizor Wallet is among the first confirmed wallet integrations. Other wallet providers will receive the improvements according to their own development schedules — each wallet must perform integration and production testing to ensure compatibility with specific platforms and UX flows. Because proof construction happens locally, real-world performance will vary by device hardware, operating system, transaction complexity, and wallet implementation.

ZEC price chart

Technical areas of improvement

Zakura Common focuses on optimizations across three tightly coupled areas of the shielded transaction flow:

1) Proof generation and zk-SNARK verification

Zero-knowledge proof generation is the heaviest local operation in a shielded wallet. By optimizing proof construction algorithms and implementation, Zakura achieved large reductions in runtime, particularly on mobile devices. On the verification side, full nodes gained roughly 4x–8x faster zk-SNARK checks, which can reduce CPU load during validation and help transactions propagate more quickly through the network.

2) Sinsemilla hashing

Sinsemilla hashing underpins many cryptographic commitments in Zcash’s shielded system. Zakura’s rework of the hashing path resulted in measurements showing more than 21x acceleration, cutting the computational burden when wallets construct private transactions and nodes verify commitments.

3) Trial decryption and wallet scanning

Wallets use trial decryption to detect which shielded outputs belong to a user when scanning blocks. Zakura’s optimizations made trial decryption substantially faster in testing, which should improve wallet sync speeds and reduce battery/CPU drain on mobile devices.

Network effects and limitations

Faster local proof construction and quicker verification both matter for user experience and node health, but they do not change block production or settlement times. Zakura Common does not alter consensus rules or block timing — it is purely a client- and node-level optimization. Faster verification could reduce pressure on validators and help with transaction propagation, but those benefits depend on how widely wallets and full nodes adopt Zakura Common.

Developers note that developer benchmarks showing sub-200 ms construction are encouraging but not definitive. Real-world transaction construction times depend on a user’s device, the complexity of the transaction, the wallet’s integration, and the local environment. Network confirmation times remain governed by block production and miner/validator behavior.

How Zakura Common relates to recent Zcash upgrades

Zakura’s release follows separate protocol-level changes introduced by Ironwood. The Ironwood update, activated through the NU6.3 network upgrade at block height 3,428,143 in July, replaced the previous Orchard pool with supply controls and an exit-only mode for the older pool. That change addressed a theoretical soundness issue in the former Orchard implementation that could have allowed undetected counterfeit ZEC creation under specific conditions. While Ironwood reworked network-level shielded infrastructure and supply controls, Zakura Common addresses client-side and node-side cryptographic performance.

Independent development and broader ecosystem growth

Zcash wallet development has become more distributed in recent months. A group of former Electric Coin Company developers formed an independent outfit and continued work on the existing Zashi codebase, initially under the CashZ name before rebranding to Zodl. That team later raised over $25 million from investors including Paradigm, a16z crypto, and Winklevoss Capital. Separately, ShapeShift has added shielded Zcash transactions to its non-custodial platform after receiving Zcash Community Grants, widening private ZEC access across different wallets and services.

Market reaction and outlook

Market movement around the Zakura announcement was modest and short-lived. ZEC initially gained about 5% and briefly traded near $839 following the release, but by Aug. 31 it was near $829 per CoinGecko after trading between roughly $808 and $888 over 24 hours. These price moves coincided with the release but do not establish causality.

Zakura Common does not replace proposed protocol changes such as NU7, which would reduce block times to approximately 25 seconds. Zakura’s team says the software is compatible with the proposed faster timing, but any protocol-level timing change still requires its own governance process and network activation before it would take effect.

For wallet developers, node operators, and privacy-focused users, Zakura Common represents a significant step toward faster, more efficient shielded transactions. If widely adopted, the library could improve wallet sync times, reduce CPU and battery load on mobile devices, and lower verification costs for full nodes — all important incremental gains for Zcash’s private-transaction ecosystem.

“Shielded wallets that use Zakura Common, and full nodes like Zakura itself, all benefit from these massive performance improvements.” https://t.co/Z7zqb7uiY5