> 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/network/how-zoka-works.md).

# How Zoka Works

At a high level:

1. A wallet owns a recovery phrase and derives wallet keys.
2. The wallet scans public chain data and detects outputs that belong to it.
3. When sending, the wallet builds a private transaction locally.
4. The network validates the transaction without exposing private participants or amounts.
5. Miners include valid transactions in proof-of-work blocks.
6. The receiver's wallet later detects and decrypts the incoming output.

## Wallets

Wallets are the privacy boundary. ZKAPriv and ZSilent Core keep secrets local and reconstruct history from public chain data.

## Nodes

Nodes validate blocks and expose chain state. Public RPC nodes are read-only infrastructure and must not receive wallet seeds, scan keys, or spend keys.

## Miners

Miners create blocks and receive block rewards directly to their `zka1...` wallet address when configured.

## Proof Generation

Private transaction proof generation is performed by wallet-side or local client code. Public nodes validate what the protocol requires; they do not need access to the sender's wallet secrets.


---

# 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/network/how-zoka-works.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.