← All insights
RESEARCHProject Tachyon

Folding Tachyon with Ragu

Introduces Ragu, the Rust recursive zk-SNARK toolkit that underpins Tachyon. It is designed without a trusted setup, using the Pasta curves and Poseidon hash already deployed.

Project Tachyon introduced Tachyon, Zcash's new shielded protocol, and Ragu, the Rust recursive zk-SNARK toolkit that underlies its cryptography. Tachyon addresses the fundamental scalability problem facing uncompromising privacy technology, and Ragu is built around Tachyon's needs and practical constraints. It aims to implement the Halo paper, which presented an ECDLP-based recursive SNARK without a trusted setup, at a production-ready level, and is described as close to an implementation of so-called recursive Bulletproofs.

As a risk-avoidance measure, Ragu relies heavily on tools Zcash has already deployed. The Pasta curve cycle, the original Poseidon hash, and the inner-product-argument-based univariate polynomial multi-commitment scheme were all used in Orchard years ago, and older cryptography from before 2021 is largely avoided. Where halo2 in Orchard uses a hand-optimized PLONK-based arithmetization, Ragu uses a simpler R1CS-like approach from the [BCCGP16] family. Cases that need FFTs or polynomial multiplication are limited to rare boundaries, such as when making a proof fully succinct.

There are other features that matter for Tachyon. In a non-uniform PCD model, each node pays only for the features it actually uses, and several sub-protocols are split into different circuits that run concurrently. Everything revolves around univariate polynomial commitments, and polynomial oracles can be queried inside application circuits. Verification performance does not depend on preprocessing, and techniques from the Halo paper accumulate evaluation claims about the public polynomials that describe the circuit. This enables a new collaborative setup that will be covered in a later post.

It also stresses high-assurance engineering. The cryptographic design and implementation were developed together with expert feedback, using audits, extensive testing and AI analysis tools, plus fuzzing and Lean-based formal verification tools. For formal verification they adopted zkSecurity's Clean framework: on the Rust side, constraints and witnesses are recorded as Lean syntax, and on the Lean side, per-gadget pre- and post-conditions are linked to soundness and completeness theorems. To do this they coordinated with zkSecurity to adjust the API and integrated automated checks into CI. Fuzzing drew on zkSecurity's research and Aztec's techniques.

Documentation is also considered essential, because formal verification proves that a program matches its specification but does not guarantee that the specification captures the intent. While developing Ragu, the team is writing a thick book explaining the cryptography; it is still unfinished, but reviewing this documentation alone turned up major improvements to the code and protocol. Tachyon will be fully specified through the ZIP process, and Ragu is also to be specified more rigorously, especially in comparison with halo2. The guideline is to concentrate complexity where it is unavoidable and keep everything else as simple as possible.

This summary is based on the original; check the original for exact details.