> For the complete documentation index, see [llms.txt](https://zka-protocol.gitbook.io/zka-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zka-protocol.gitbook.io/zka-protocol-docs/introduction/overview.md).

# Overview

## 🟣 What is ZKAP?

ZKAP (Zero-Knowledge Anonymous Protocol) is a **privacy interaction layer** that allows any blockchain application — DEXs, wallets, RFQ systems, bridges, agents — to execute actions **without exposing identity or metadata**.

Blockchains today reveal:

* sender address
* signature
* calldata
* behavior patterns
* routing & intent structure
* on-chain history

ZKAP removes all of that.

***

### 🔐 ZKAP = Privacy at the transport layer

ZKAP sits *under* applications and *above* the execution layer:

Applications (DEX, Wallet, Agents) ↓ ZKAP — Anonymous Interaction Layer ↓ Blockchain (EVM, SVM, MoveVM, L2 Rollups)

yaml Copy code

Instead of sending raw transactions, users and agents send:

* **encrypted private frames**
* **zero-knowledge validity proofs**
* **anonymous ephemeral identities**

Applications only see:

> “A valid action exists — but we don’t know who performed it.”

***

### 🧩 Why this matters

Without ZKAP:

* users are trackable
* agents are identifiable
* swaps & intents leak metadata
* strategies can be front-run
* cross-chain messages reveal routing
* DEX orderflow becomes predictable

With ZKAP:

* identities disappear
* calldata is encrypted
* actions become unlinkable
* cross-chain interactions stay hidden
* agents operate keylessly and privately

***

### 🟣 What ZKAP enables

ZKAP is designed to serve as the **privacy engine** for the next generation of Web3:

* Anonymous DeFi interactions (DEX, AMM, RFQ)
* Private cross-chain intents & routing
* Keyless, identity-less AI Agents
* Private governance & proposal actions
* Backrun-proof trading strategies
* Private bridge commands
* Cross-rollup private messaging

If your application needs **validity + anonymity**, ZKAP provides it.

***

### 🚀 Who is ZKAP for?

* **Developers** building private wallets, DEXs, RFQ, bridges
* **Agent frameworks** needing identity-less execution
* **L2 rollups** requiring a standardized privacy layer
* **Teams** building private automation pipelines
* **Users** who want real anonymity in Web3

***

### 🌐 Summary

ZKAP transforms blockchain interactions from:

❌ identity-first\
❌ signature-heavy\
❌ metadata-visible

→ into:

🟣 anonymous-by-default\
🟣 encrypted-by-default\
🟣 validated-by-ZK

ZKAP is not a mixer, not a privacy app, not a wallet.

> **ZKAP is the transport layer for anonymous execution in Web3.**


---

# 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, and the optional `goal` query parameter:

```
GET https://zka-protocol.gitbook.io/zka-protocol-docs/introduction/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.