Panel: Zero Knowledge in the Enterprise
summary
Panelists contrast pragmatic deployments with long‑term cryptography: enterprise platforms pick SGX first ZK later to run existing Java apps now and plan gradual migration to recursive ZK proofs; banks deploy identity mixer and use ZK for off‑chain verification and batching to scale; one team reuses the Zcash trusted setup for a production mixer. Major obstacles are implementation flaws (bad randomness, timing attacks), tooling (compilers from Java to constraints), huge circuit sizes — billions of gates — and the need for an open governance foundation to manage risk.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:35Panel Introductions
- 2:43Data Privacy
- 3:30Bank Vision
- 4:07Data for Banks
- 7:15Recursive proofs
- 8:03Zero knowledge proof
- 9:23How to analyze zero knowledge proof
- 12:05Why not use zero knowledge proof
- 13:45Timelines
- 22:33Private Blockchains
- 27:20The value of a network
- 30:50The difficulty of knowing if it breaks
- 32:38A strong weapon in the hand
- 33:36Talking to regulators
- 36:29Bridging theory implementation
- 40:38Auditing systems
- 42:44Governance model
- 43:42The hardest problem
- 44:45The most important thing
- 45:51Theoretical issues
- 47:42No standards
related talks
17mZK for the Enterprise - Quod Erit Demonstrandum (What Will Need to be Proven)
01h 26mPanel Discussion: The Challenges and Best Practices of Deploying Zero-Knowledge Proofs
30mPractical Zero Knowledge Proofs
51mWhy you shouldn't trust me
33mAn Introduction to Zero Knowledge Proofs
32mSoK: Private Programmability on Blockchain Systems
33mEducational Challenges in the Ever-Evolving Space of Zero-Knowledge
23mYour Game Will Suck Without Zero Knowledge Proofs