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

# Overview

Arcan splits one confidential transfer across four places. None of them is allowed to skip the others.

```
app  ->  Robinhood  ->  coprocessors
              |
              v
         access list
```

## The path of an amount

1. The SDK encrypts the amount with the Arcan public key and attaches an input proof.
2. The user calls the contract on Robinhood. From and to are plaintext. The amount is a ciphertext.
3. The contract checks the proof, updates balances as handles, and writes the access list.
4. Coprocessors run `add` and `sub` on the ciphertext and commit the new ciphertext.
5. The wallet shows `****` until an allowed account decrypts.

The result is publicly recomputable. A third party can replay the recorded operation on the ciphertext and reach the same handle. They still cannot read the number.

## Pages

* [FHE library](/protocol/library.md) is the operation set contracts call.
* [Host chain](/protocol/host.md) is Robinhood, which stores handles.
* [Coprocessors](/protocol/coprocessors.md) run the FHE.
* [Gateway](/protocol/gateway.md) moves ciphertexts and decrypt requests between the user, the host, and the coprocessors.
* [Opening a handle](/protocol/keys.md) is how an allowed account gets the plaintext.


---

# 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.arcan.finance/protocol/overview.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.
