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

# What is Okkult

Understand what Okkult Protocol does and who it serves.

## What is Okkult

Okkult Protocol is privacy infrastructure for Ethereum.

Public blockchains make every transaction easy to inspect.

That helps with transparency. It also means balances, transfers, and activity can be visible to anyone.

Okkult solves this by adding privacy and compliance tools to Ethereum.

It lets users prove what matters without exposing sensitive information. That includes compliance status, asset movements, identity claims, and voting choices.

In simple terms, Okkult gives users more privacy on-chain without giving up control of their assets or the ability to prove compliance when needed.

### What Okkult does

* Protects sensitive on-chain activity
* Helps users prove compliance privately
* Lets users shield and transfer assets
* Supports private governance
* Supports privacy-preserving identity verification

### Protocol stack

| Module            | What it does                                                   |
| ----------------- | -------------------------------------------------------------- |
| **Okkult Proof**  | Creates a zero-knowledge compliance proof for a user.          |
| **Okkult Shield** | Lets users shield assets and use private balances.             |
| **Okkult Relay**  | Helps submit supported transactions through relayers.          |
| **Okkult Vote**   | Enables private on-chain voting.                               |
| **Okkult ID**     | Lets users prove identity claims without revealing everything. |
| **Okkult Mail**   | Verifies email-based claims with privacy protection.           |

### Key properties

| Property                | What it means                                       |
| ----------------------- | --------------------------------------------------- |
| **Non-custodial**       | Users keep control of their assets.                 |
| **Privacy-first**       | Sensitive details stay hidden.                      |
| **Compliance-aware**    | Users can prove compliance without full disclosure. |
| **Client-side proving** | Proof generation runs in the browser.               |
| **Open source**         | The protocol is released under the MIT license.     |
| **Ethereum-based**      | The system runs on Ethereum Mainnet.                |

### Who Okkult is for

* Users who want more privacy in crypto
* Developers building privacy-aware apps
* Teams that need compliance and on-chain verification

### Next Steps

* [Quick Start](/getting-started/quick-start.md)
* [Connect Wallet](/getting-started/connect-wallet.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.okkult.io/getting-started/what-is-okkult.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.