> For the complete documentation index, see [llms.txt](https://docs.orbisprotocol.com/orbis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbisprotocol.com/orbis/technology/zk-snarks.md). # zk-SNARKs “zk-SNARK” stands for “**zero-knowledge succinct non-interactive argument of knowledge**.” zk-SNARKs are a type of zero-knowledge proof. What is a zero-knowledge proof? It is a cryptographic technique, where one party (The Prover) can prove that a specific statement is true to the other party (The Verifier) without disclosing any additional information. A zk-SNARK is a type of zero-knowledge proof that has 3 core characteristics. * “Succinctness”, which means the proof is not lengthy. This property reduces the costs of storing and transmitting proofs * “Non-interactive”, meaning that a zk-SNARK consists of a single message as opposed to an interaction. * “Zero-knowledge”, meaning that the proof does not reveal any information beyond the statement that it proves to be true. Leading-edge zk-SNARK theories also provide the benefit of inexpensive proof checking. Even when the proof is expensive to generate, the proof’s size and the complexity of checking the proof do not increase. --- # 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.orbisprotocol.com/orbis/technology/zk-snarks.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.