Zcash Starts Building Tachyon Into Its Private Payment Stack

Zcash developers are integrating Udon, a cryptography component of the proposed Project Tachyon upgrade, into Zakura Common as they begin testing a new architecture for scaling private payments. The work is not a live network upgrade, but it marks a significant step toward a system designed to make shielded transactions practical at much greater volumes.

The Tachyon team announced that it is upstreaming recursive proof technology into Zakura Common, a shared cryptography library used by Zakura and other Zcash projects. The announcement also introduces Udon, a Rust crate that moves additional Tachyon related calculations into the existing software base.

That distinction matters. Zcash has not activated Tachyon, and the current work remains subject to further development, testing and security review. Udon gives developers a common place to implement the proposed architecture, measure its performance and identify the engineering problems that must be solved before any network deployment could be considered.

Scaling private transactions

Shielded Zcash transactions are designed to hide the sender, recipient and amount. Nodes must still verify that each transaction is valid, but they do so by checking cryptographic proofs rather than inspecting the payment details directly. This privacy model creates a computational burden that becomes more difficult to manage as transaction activity grows.

Project Tachyon’s official overview presents the upgrade as an effort to support encrypted money at planetary scale. Its core approach is to combine proofs from multiple transactions, allowing individual nodes to receive and verify a smaller representation of the underlying payment activity. The project also aims to reduce the amount of validator state that the network must maintain.

The long term target is more than 50,000 private payments per second. That would place Zcash in a very different operating environment from its current one, where shielded transaction activity is far below the proposed capacity. The gap is important because it gives developers time to address the architecture before demand makes existing limitations more urgent.

The challenge is that high throughput does not eliminate cryptographic work. Instead, Tachyon is intended to reorganize it. Many individual proofs would be combined into a larger recursive proof, which nodes could then verify more efficiently. The approach could reduce the amount of data that each node must receive and process, but it may require more memory and more specialized proving infrastructure on the side that generates the combined proof.

Performance gains and trade-offs

Earlier improvements to Zakura Common reportedly reduced private proof creation times from more than three seconds to under 200 milliseconds in some tests. Integrating Udon into that optimized library allows developers to build on those gains instead of maintaining a separate experimental implementation.

The performance trade-off is not simply a matter of making every operation faster. At the proposed transaction rate, existing cryptographic methods could require each Zcash node to process more than 500 megabytes of data per second. That level of throughput would create serious demands for bandwidth, storage access and processor capacity, potentially narrowing the group of users able to operate full nodes.

Tachyon’s value proposition is therefore tied to network accessibility as much as raw transaction capacity. If proof aggregation works as intended, nodes could validate the same economic activity while handling less data. That could help preserve a broad validator base, a central consideration for a privacy network whose security depends on independent participants verifying the chain.

The cost shifts toward proof generation. Producing an aggregated proof requires additional memory and potentially more capable hardware. Developers must determine whether that burden can be managed without concentrating transaction production among a small number of specialized operators.

An early step, not a capacity upgrade

The project’s public GitHub repository provides the implementation source for the Tachyon Rust library. Its significance is practical: the proposal is moving from a high level scaling concept toward code that can be compiled, tested and reviewed by developers outside the core team.

That process will be essential for a privacy system. Cryptographic optimizations can introduce subtle flaws, and recursive proof systems require extensive testing before they can be trusted with real funds. The code must also fit into the broader Zcash software ecosystem without creating incompatible assumptions between wallets, nodes and applications.

Network data will provide another test. The ZecStats public API documents full node derived data fields for tracking shielded transaction activity, giving developers and observers a way to compare real usage with the capacity Tachyon seeks to provide.

For now, the Udon integration is best understood as infrastructure preparation. It does not deliver an immediate increase in Zcash throughput, nor does it guarantee that the proposed design will reach production. Its importance lies in addressing a strategic question early: whether a privacy focused blockchain can preserve strong confidentiality while reducing the computational and data costs that threaten to limit adoption.

If successful, Tachyon could make private payments more scalable without requiring users to trade away privacy. If its proving and memory requirements remain too high, however, the network may face a different form of centralization, with fewer participants able to create or verify transactions. The next phase of development will determine which side of that trade-off ultimately defines Zcash’s growth.