In this session, we discuss design patterns and tradeoffs for zkSNARK-based decentralized apps. We dig into a few case studies, such as design decisions for TornadoCash and potential variants.
We recommend you inspect the TornadoCash core codebase here.
Additional Notes, Links, References
- rapidsnark, a fast natively-implemented SNARK prover: https://github.com/iden3/rapidsnark
- plonkit, a toolkit for handling circom circuits with a PLONK proving system: https://github.com/fluidex/plonkit
- WJ’s benchmarks for various cryptographic tree accumulators: https://ethresear.ch/t/gas-and-circuit-constraint-benchmarks-of-binary-and-quinary-incremental-merkle-trees-using-the-poseidon-hash-function/7446