Standardization Interview – Eran Tromer
summary
Aims to standardize Zero Knowledge Proofs by defining concrete interfaces so implementations interoperate, not just describe schemes; the implementation track targets APIs that let application code pick, modify and compare different proof engines. Notes rapid proliferation of incompatible schemes and implementations, argues for a plug-and-play interface and shared primitives to enable mix-and-match deployment. Positions the effort as early but practical, with follow-up workshops to resolve engineering and specification challenges.
AI-written summary · about
chapters (4)
- 0:00Can you explain the potential of zero-knowledge proof according to you?
- 0:19and can you explain what you are expecting from this track?
- 0:40Why do you think there is a great need to standardize this technology?
- 1:23Do you want to add anything?
related talks
20mThe Evolution of ZKProof.org
35mEfficient Zero Knowledge Protocols: The Modular Approach
24mTooling Infrastructure for Zero Knowledge Proofs
26mApplications of Zero Knowledge Proofs in the Banking Industry
59mCommit-and-Prove Zero-Knowledge Proof Systems and Extensions
30mPractical Zero Knowledge Proofs
44mBilinear Pairings-based Zero-Knowledge Proofs
01h 26mPanel Discussion: The Challenges and Best Practices of Deploying Zero-Knowledge Proofs
