> For the complete documentation index, see [llms.txt](https://zokanetwork.gitbook.io/zokanetwork/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokanetwork.gitbook.io/zokanetwork/privacy/zero-knowledge-proofs.md).

# Zero-Knowledge Proofs

Zero-knowledge proofs let one party prove that a statement is valid without revealing the private data behind the statement.

In ZOKA, proof infrastructure supports private transfer validation. The network can validate the required rules while the public explorer does not learn the private sender, receiver, or amount.

## Why ZOKA Uses ZK

* Preserve private wallet data.
* Keep transactions verifiable.
* Prevent invalid spends.
* Support double-spend prevention through nullifiers.

## Important Boundary

Zero-knowledge proofs protect transaction data. They do not hide every network metadata signal. Timing, IP-level behavior, public RPC usage, and address reuse can still matter operationally.

## Release Awareness

Proof systems depend on the active circuit, verification keys, and activation rules for the release. Documentation and integrations should track the current release branch instead of assuming that every development profile is active on public nodes.


---

# 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:

```
GET https://zokanetwork.gitbook.io/zokanetwork/privacy/zero-knowledge-proofs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.