> 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/threat-model.md).

# Threat Model

ZOKA is designed to reduce public-chain analysis of private user payments.

## Resistance Goals

* **Chain analysis resistance**: private transaction records do not expose sender, receiver, or amount.
* **Address tracking resistance**: the explorer does not expose full public address histories for private wallet identities.
* **Balance tracking resistance**: balances are wallet-side and not public explorer data.
* **Double-spend resistance**: nullifiers prevent reuse of spent notes.

## Metadata Considerations

Privacy is not only cryptography. Users should also consider:

* RPC endpoint choice.
* Network timing.
* Reusing public identities with the same receive address.
* Publishing screenshots with balances or QR codes.
* Sharing scan keys or recovery material.

## Non-Goals

The public chain still exposes block production, timestamps, proof-of-work, hashes, commitments, nullifiers, and other consensus data.


---

# 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/threat-model.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.