Zcash developers have started folding Project Tachyon code into Zakura Common, the codebase that underpins the privacy-focused cryptocurrency's network. The integration marks the first concrete step toward a long-term target of processing more than 50,000 private payments per second.
The work is early, and the throughput goal sits well ahead of what the network handles today. But the decision to begin merging Tachyon into Zakura Common gives the effort a defined home inside Zcash's core infrastructure rather than leaving it as a standalone experiment.
What Project Tachyon is meant to do
Project Tachyon is the name attached to Zcash's push for far higher transaction throughput without giving up the shielded transactions that define the coin. Private payments are the feature Zcash is best known for, and they're also the most computationally expensive to produce. Scaling them has always meant balancing speed against the cryptography that keeps sender, receiver, and amount hidden.
The stated goal of more than 50,000 private payments per second is a throughput figure, not a promise about a specific launch date. For context, that number is orders of magnitude beyond what the current Zcash mainnet clears in private transactions. Reaching it would require changes at multiple layers of the stack, which is why the work is being staged rather than shipped in one release.
Why Zakura Common matters for the rollout
Zakura Common isn't a side project. It's the shared code layer that Zcash's node software and related tooling draw from, which makes it the natural place for Tachyon's components to land if they're going to reach operators, wallets, and exchanges down the line.
Integrating into Zakura Common also means Tachyon's code will be reviewed and maintained alongside the rest of Zcash's core, rather than living in a separate repository that could drift out of sync. That matters for a change this size. Throughput improvements that touch consensus rules or transaction formats have to be coordinated across every implementation in the ecosystem, and a fragmented codebase makes that coordination harder.
The developers haven't said which specific Tachyon components are going into Zakura Common first, or how long the full migration will take. The integration is described as ongoing.
The gap between a target and a working network
50,000 private payments per second is a design target. Getting from a target to a live network involves benchmarking, testnet runs, audits, and a governance process for activating any consensus changes. None of those steps have been scheduled publicly, and the facts here don't include a timeline.
There's also the question of what "private payments per second" actually measures in practice. Shielded transactions vary in complexity depending on the addresses and memo fields involved, so a headline throughput number typically reflects a specific transaction profile under controlled conditions. How that translates to real-world traffic on a decentralized network is a separate problem, and one that Zcash developers will have to demonstrate rather than assert.
What to watch next
The immediate signal is code movement: Tachyon components appearing in Zakura Common, followed by whatever test harnesses and benchmarks the team publishes to back up the throughput claim. Until there's a testnet result or a proposed activation path, the 50,000 figure stays a goal on paper.
Zcash isn't the only privacy coin chasing scale, and it isn't the only project trying to keep strong privacy guarantees while raising throughput. What sets this effort apart is the decision to build inside the existing core codebase instead of forking away from it. Whether that choice speeds up delivery or slows it down under the weight of consensus review is the open question the integration will answer.
