Zcash Moves Tachyon Components Into Zakura Common to Advance Faster Private Payments
Key Takeaways
- •Zcash developers have begun migrating Project Tachyon components into Zakura Common, the ecosystem's shared cryptographic codebase, a step that affects developer infrastructure rather than end-user features.
- •Project Tachyon aims to speed up shielded payments by using proof-carrying data for more efficient transaction aggregation and an oblivious synchronization design that protects nullifiers when wallets prepare spends.
- •The first release of the integration is Udon, a Rust component that unifies performance-sensitive arithmetic from older libraries and allows applications to configure their own memory and parallel-processing limits.
- •Shielded transactions currently impose two scaling burdens on Zcash: extra computation to create and verify privacy proofs, and a continually growing set of nullifiers that validators must retain.
- •Tachyon is a proposed upgrade distinct from the November 5 NU7 target, with 11 Zcash Improvement Proposals still outstanding, the Ragu framework unaudited, and any Mainnet activation dependent on community approval.

Zcash developers have begun integrating components of Project Tachyon, a proposed upgrade aimed at enabling faster private payments, into Zakura Common, a shared cryptographic codebase intended to serve the wider ecosystem. According to a September 28 developer post, the step marks the start of a code migration rather than a network activation.
For ZEC holders, nothing changes today. Users do not receive a new shielded-transaction feature simply because Tachyon components are entering Zakura Common. The immediate users are developers, who are preparing the cryptographic foundation that wallets, nodes, and future protocol work could draw on later.
That preparation matters because private payments place heavier demands on software than ordinary transparent transfers, and those demands become harder to manage as usage grows.
Private payments carry two scaling costs
Shielded Zcash transactions use cryptographic proofs to show that a transfer follows the network's rules without publicly revealing the sender, recipient, or amount. Creating and verifying those proofs takes more work than checking a transparent transfer. In effect, shielded payments trade extra computation for confidentiality, and that trade-off shapes both wallet performance and the amount of data validators must store.
A longer-term infrastructure cost also exists. To prevent the same shielded funds from being spent twice, validators track unique values called nullifiers. Project Tachyon's technical overview says that this set continues to grow under the current design, increasing the amount of consensus data validators must retain.
Tachyon is designed around proof-carrying data, a method for compressing the evidence that a computation was performed correctly. The proposal aims to let block producers aggregate shielded transactions more efficiently, while its “oblivious synchronization” design would help wallets prepare the information needed for spending without revealing their actual nullifiers to the remote service involved.
These are ambitious design goals. They address both the cost of checking a private payment and the state burden created after that payment has been accepted.
Why Zakura Common sits at the center of the work
Research implementations can demonstrate that a cryptographic design is possible. Wallet and node software must meet a different standard: maintainable code, predictable use of memory and computing resources, reliable testing, and a clear path for other teams to integrate the work.
Zakura Common is intended to serve as the common cryptographic base for that effort. The developers say Tachyon shares underlying mathematical components with existing Zcash cryptography, even though its recursive proofs create additional requirements. Consolidating those overlapping components can reduce duplicated code and allow a single optimization to benefit more than one part of the ecosystem — in practice, the shared base is what turns an individual improvement into an ecosystem-wide one.
The first release in this process is Udon, a Rust component that combines performance-sensitive arithmetic previously divided between older libraries. Its design lets applications set their own memory and parallel-processing limits, which is relevant because a mobile wallet, a full node, and a server do not operate with the same hardware resources. That flexibility is directly relevant to shielded payments, where preparing a spend involves real computational work on the wallet side.
That does not, on its own, guarantee faster transactions for users. It gives future implementations a more direct route to optimized code without carrying as many compatibility layers between separate libraries.
Tachyon still needs specifications, review, and network approval
Tachyon sits further out on Zcash's technical roadmap than the next scheduled network changes. Coindoo previously reported the November 5 target for the NU7 upgrade, which concerns nearer-term protocol work. The new Zakura Common integration instead focuses on building cryptographic components that a later Tachyon proposal could use, so the two efforts remain separate tracks on the same roadmap.
The Project Tachyon website describes Tachyon as a proposed Zcash upgrade. Its activation would require community approval rather than a developer team simply shipping a wallet update.
The project's public implementation tracker currently identifies 11 Zcash Improvement Proposals, covering the shielded protocol, transaction format, aggregation, synchronization, and eventual deployment. That figure illustrates the scale of the remaining work: the code migration is one part of a broader protocol effort.
Security review also remains essential. The Ragu proof-carrying-data framework used for Tachyon states that it is under heavy development and has not undergone an audit. Public code is valuable because it allows technical scrutiny; it should not be treated as that the system is ready for production use.
What would show real progress from here
Readers do not need to follow every cryptographic library change. A few later milestones would show whether this work is becoming usable private-payment infrastructure:
- Reproducible benchmarks: results that identify the hardware, transaction type, and testing conditions.
- Independent review: audits or formal verification covering the new implementation and its assumptions.
- Wallet and node integration: releases that explain which users benefit and under what conditions.
- Protocol progress: completed specifications and a defined community process for a potential upgrade.
Making privacy practical at scale
Zcash's developers are treating privacy scaling as an infrastructure problem, and faster proof work is only one part of it. Wallets need to remain usable, validators need sustainable hardware requirements, and the cryptographic assumptions need to withstand careful review.
Moving Tachyon into Zakura Common does not settle those questions. It makes the work more concrete by putting research components into a shared software foundation that other Zcash developers can test and build on. The next meaningful evidence will come from review, implementation, and eventual user-facing releases, not from an aspirational transaction-per-second figure alone.
This article is provided for informational purposes only and does not constitute financial or investment advice. Project Tachyon remains under development and would require further technical work and community approval before any Mainnet activation.