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

# Introduction

Privacy is a critical concern in blockchain technology, where the transparency of decentralized networks conflicts with the confidentiality users often expect. Unlike traditional systems with access controls and encryption, blockchain platforms—particularly the EVM—lack built-in privacy, exposing all data across the network. This openness can deter users and industries that require discretion, risking data exposure and regulatory issues. To address these challenges, COTI is introducing [garbled circuits](/coti-documentation/how-coti-works/introduction/garbled-circuits.md) to enable private transactions, balancing blockchain transparency with the confidentiality essential for broader adoption, regulatory compliance, and respect for user privacy.


---

# 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://docs.coti.io/coti-documentation/how-coti-works/introduction.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.
