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

# Transaction Lifecycle

## 1. Create

The sender's wallet selects spendable private notes and a recipient `zka1...` receive address.

## 2. Build Proof Data

The wallet constructs the private transfer locally. Private metadata remains in the wallet boundary; the public transaction does not reveal sender, receiver, or amount.

## 3. Broadcast

The locally built transaction is submitted to the network through a node or RPC endpoint. Public RPC should receive transaction payloads, not wallet secrets.

## 4. Validate

Nodes validate consensus rules, proof data, nullifiers, commitments, and block structure.

## 5. Include in Block

A miner includes the transaction hash or body data required by the active protocol format in a proof-of-work block.

## 6. Recover by Receiver

The receiver's wallet scans chain data, detects outputs that belong to its scan key, and decrypts the data needed to update local balance and recent activity.


---

# 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/transaction-lifecycle.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.