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

# Security

ZOKA's security model combines cryptography, proof-of-work consensus, local wallet custody, encrypted storage, and conservative operational practices.

## Security Philosophy

* Keep wallet secrets local.
* Validate public chain data.
* Avoid transparent leakage of private transfer metadata.
* Treat release, setup, and signing materials as sensitive.

## Security Posture

The project combines several sensitive areas: proof-of-work consensus, zero-knowledge proof validation, wallet key derivation, encrypted local storage, mobile release signing, desktop process orchestration, and public RPC surfaces.

Each area has a different failure mode. A public website bug should not expose wallet secrets. A desktop log should not contain a recovery phrase. A node should reject invalid blocks even if a wallet or explorer displays them.

## Practical Rule

When in doubt, keep secrets local, keep public data minimal, and document the exact release behavior instead of making broad security claims.


---

# 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/security.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.