> 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/usdanc/anc.md).

# $ANC

$ANC pays for Arcan. There is no venture capital in the project. Development is funded by trading fees on $ANC, and that is its major use case.

The confidential token standard is a separate thing. ERC-7984 seals amounts. $ANC does not. $ANC is the fee stream that keeps the protocol moving without a fund taking a stake.

When $ANC trades, the fees from that trading go back into building: the contracts, the coprocessors, and the SDK. The work stays funded by the people who use it.

## Buy

$ANC is on Pons: [Buy $ANC](https://ponsfamily.com/launchpad/0xf11d9b4ecc3e07f0beef0f176dd641d2e0fc3f37).

Contract `0xf11d9b4ecc3e07f0beef0f176dd641d2e0fc3f37`.


---

# 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/usdanc/anc.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.