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

# $CNC Basics

### Why does CNC exist?

Ultimately, CNC allows users to shift liquidity of an asset across multiple Curve pools. This is achieved by Conic DAO [liquidity allocation votes](/conic-finance/governance/liquidity-allocation-vote-lav.md) (LAVs), which update the liquidity allocation weights of each Curve pool that is used by Conic Omnipools. In order to be eligible to participate in LAVs, a holder must first[ lock CNC](/conic-finance/usdcnc-token/locking-usdcnc.md) for vlCNC. 

### How to get CNC?

* Liquidity providers can receive CNC by staking their Conic Omnipool LP tokens
* CNC is emitted to depositers during rebalance periods to incentivize rebalancing of Omnipools
* CNC may be purchased on AMMs (e.g. the [Curve CNC/ETH pool](https://etherscan.io/address/0x838af967537350d2c44abb8c010e49e32673ab94))

### What is the maximum CNC supply?

10,000,000 CNC

### What is the utility of CNC?

Please refer to the below:

{% content-ref url="/pages/LLFWkNvQTVjuav317OMM" %}
[Locking $CNC](/conic-finance/usdcnc-token/locking-usdcnc.md)
{% endcontent-ref %}


---

# 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.conic.finance/conic-finance/usdcnc-token/usdcnc-basics.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.