> 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/build.md). # What you can build The confidential token standard is an ERC-20 with the amounts encrypted. Balances are handles. Transfers move those handles. The wallet shows `****` unless the account is allowed to open it. The calls are in [Confidential token standard](/apps/token.md). Anything that moves a number can keep that number sealed. Addresses can stay public. The amount does not. ## On the standard * **Confidential tokens.** A confidential balance and a confidential transfer. * **Confidential DEX.** A swap where the trade size stays encrypted. * **Confidential AMM.** Pool reserves and swap amounts stay handles. The curve still runs. The size does not hit the book. * **Confidential NFTs.** A mint, a sale, or a bid where the price stays sealed. * **Confidential lending.** Collateral and debt stored as handles. A liquidation check uses `FHE.select`, so the shortfall is not published. * **Confidential auctions.** Bids stay encrypted until the contract marks the winning price public. * **Confidential payroll.** Each payment is a sealed transfer. The salary is not on the explorer. * **Confidential distributions.** A pool split across holders without listing each share. * **Confidential real-world assets.** The position and the terms stay ciphertext. The asset record can stay public. * **Sealed votes.** A tally on encrypted ballots. The result can be opened when the vote ends. Each of these is a contract on the same token standard: encrypt the amount, update handles, and name who may decrypt. Robinhood stores the handles. Coprocessors run the FHE. --- # 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/build.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.