Panel Discussion: The Challenges and Best Practices of Deploying Zero-Knowledge Proofs
summary
Panelists report real deployments: a private rollup on Ethereum using recursive zk-SNARKs (Aztec’s PLONK-style system), Hermez running payments on Groth16, and Zcash migrating to Halo for a no‑trusted‑setup upgrade; implemented proof systems include Sonic, Marlin, Pickles and Halo2. Key tradeoffs are arithmetization (PLONK’s custom gates vs R1CS) and trusted setup versus transparent/no‑setup; recursion is essential for privacy and parallel proving. Audits, dual implementations, and cloud/GPU proving (not yet ASIC ubiquity) determine whether these builds actually work.
AI-written summary · about
chapters (5)
- 0:00Start
- 32:54Does Having a Trusted Setup Matter
- 35:07Advantages over Having Universal Setup
- 52:29Smart Contracts
- 1:24:25Announcements
related talks
30mPractical Zero Knowledge Proofs
51mPanel: Zero Knowledge in the Enterprise
51mWhy you shouldn't trust me
44mZero-Knowledge Proofs: Simultaneously ensuring integrity and privacy
22mDIZK: A Distributed Zero Knowledge Proof System
32mSoK: Private Programmability on Blockchain Systems
26mApplications of Zero Knowledge Proofs in the Banking Industry
48mzkSNARKs — Cryptographic Proofs for Scaling and Security Challenges
