> For the complete documentation index, see [llms.txt](https://docs.nezohub.com/nezohub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nezohub.com/nezohub/overview/research/zero-knowledge-proofs.md). # Zero-Knowledge Proofs ### Genesis Zero-Knowledge Proofs (ZKPs) were conceptualized in the 1980s by Shafi Goldwasser, Silvio Micali, and Charles Rackoff. Their seminal work [*The Knowledge Complexity of Interactive-Proof Systems*](https://dl.acm.org/doi/pdf/10.1145/22145.22178) introduced a cryptographic method where one party could prove the truth of a statement to another party without revealing any information beyond the statement's validity. When the technique was first proposed, even the cryptography community declared it to be impractical, even though it was regarded as a theoretical advance. Recent years have witnessed several advancements, particularly the work of numerous web3 projects like ZCash and Aztec, which have improved the performance of zero-knowledge proof systems in a manner similar to Moore's Law. ### What is a Zero-Knowledge Proof? A zero-knowledge proof system is a cryptographic protocol that allows one party, known as the prover, to demonstrate the validity of a statement to another party, known as the verifier, without revealing any additional information beyond the fact that the statement is true. \ \ This concept ensures that the prover can convince the verifier of the truth of a claim without disclosing any sensitive or private information related to the claim itself. In essence, zero-knowledge proofs enable secure and confidential interactions between parties while preserving data privacy. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nezohub.com/nezohub/overview/research/zero-knowledge-proofs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.