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

# Welcome

**Welcome to the Zama Confidential Blockchain Protocol Docs.**

The docs aim to guide you to build confidential dApps using Fully Homomorphic Encryption (FHE).

## Where to go next

If you're completely new to FHE or the Zama Protocol, we suggest first checking out the [**Litepaper**](https://docs.zama.ai/protocol/zama-protocol-litepaper)**,** which offers a thorough overview of the protocol.

Otherwise:

🟨 Go to [**Quick Start**](https://docs.zama.ai/protocol/solidity-guides/getting-started/quick-start-tutorial) to learn how to write your first confidential smart contract using FHEVM.

🟨 Go to [**Solidity Guides**](https://docs.zama.ai/protocol/solidity-guides) to explore how encrypted types, operations, ACLs, and other core features work in smart contracts.

🟨 Go to[ **Zama SDK** ](/protocol/sdk/overview.md)to build a confidential dApp that can shield, transfer, and unshield tokens with Fully Homomorphic Encryption.

🟨 Go to [**Protocol Apps**](/protocol/protocol-apps/readme.md) to understand governance, staking, confidential wrappers, and registry contracts for operators and token holders.

🟨 Go to [**FHE on Blockchain**](/protocol/protocol/overview.md) to learn the architecture in depth and understand how encrypted computation flows through both onchain and off-chain components.

🟨 Go to [**Examples**](https://docs.zama.org/protocol/examples/) to find reference and inspiration from smart contract examples and dApp examples.

## Help center

Ask technical questions and discuss with the community.

* [Community forum](https://community.zama.ai/c/fhevm/15)
* [Discord channel](https://discord.com/invite/zama)
* Reach us at <zama@support.org>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zama.org/protocol/readme.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 `automate deployments from our CI pipeline` 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.