> 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/apps/overview.md). # Overview Arcan apps are contracts that move value without publishing the amount. The protocol pieces underneath them are the same: handles on Robinhood, FHE on coprocessors, an access list for who may open a result. The confidential token standard is that contract: ERC-20 calls, encrypted amounts. [What you can build](/apps/build.md) lists the apps that sit on it, from a confidential token to a confidential DEX, AMM, or NFT. ## Included here * [What you can build](/apps/build.md). * [Confidential token standard](/apps/token.md), the ERC-7984 shape. * [Wrappers](/apps/wrappers.md), contracts that put an existing asset behind a sealed balance. ## How an app should behave * Addresses of the parties can be public. * Amounts stay handles. * The holder can decrypt their own position. * An auditor or regulator is added with `FHE.allow` only when the product needs that name. * A public decrypt is reserved for a value the app has decided to reveal. Compose apps by passing handles, not by decrypting in the middle. The shared public key is what makes a token and a wrapper able to use the same ciphertext. --- # 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/apps/overview.md?ask=&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.