A Certifying Compiler for Zero-Knowledge Proofs of Knowledge Based on Sigma-Protocols
By José Carlos Bacelar Almeida, Endre Bangerter, Manuel Barbosa, S. Krenn, Ahmad-Reza Sadeghi, Thomas Schneider. 2010
61 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Computer Networks and Communications, Information Systems
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Dan Boneh
- Srinath T. V. Setty
- Mariana Raykova
- Bryan Parno
- Craig Gentry
- Michael Naehrig
- Michael Walfish
- Jon Howell
In Computer Networks and Communications
- Zheng Yan
- Xixun Yu
- Michael Backes
- Christina Garman
- Matthew D. Green
- Craig Gentry
- Mariana Raykova
- Aviel D. Rubin
In Information Systems
- Mariana Raykova
- Craig Gentry
- Bryan Parno
- Jon Howell
- Zheng Yan
- Michael Naehrig
- Matthew D. Green
- Athanasios V. Vasilakos
Citations in the corpus
- Geppetto: Versatile Verifiable Computation (2015, methodology): “Zero Knowledge Several systems compile high-level functions to zero-knowledge (ZK) proofs [1, 4, 42].”
- Pinocchio: Nearly Practical Verifiable Computation (2013, methodology): “Several systems provide compilers for zero-knowledge (ZK) proofs [62–64].”
- A Survey of Verifiable Computation (2017, background): “Other concurrent work [12, 62, 71] tried to solve this open problem of balancing the requirement of confidentiality and efficiency with other techniques and had a better performance than [46].”
- Automated Synthesis of Privacy-Preserving Distributed Applications (2011, methodology): “We proved that the implementations output by the compiler enforce the intended authorization policies and we conducted an experimental evaluation to demonstrate the feasibility of our approach.”
- Charm: a framework for rapidly prototyping cryptosystems (2013, methodology): “There have been several elegant implementations of a small number of new primitives [52, 43, 11] as well as some tools for protocol development [45, 5, 44, 32, 37, 39].”