> For the complete documentation index, see [llms.txt](https://cyelefi.gitbook.io/cyclefi-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyelefi.gitbook.io/cyclefi-protocol/tokenomics/cyf-token.md).

# CYF Token

CYF tokens can be utilized for staking CYF to acquire veCYF. The daily emission is set at 50,000, and the CYF supply will not increase unless a relevant governance proposal is initiated and successfully passed. In the event of a vote to increase the supply cap, the change is subject to a 14-day time lock before taking effect.

The total supply of COF now is 100,000,000

### veCYF

veCYF, serving as the protocol governance token, bestows increased voting power on protocol governance with a higher veCYF holding. Users can obtain veCYF by locking CYF, and holding veCYF provides users with protocol income and CYF rewards. veCYF tokens are minted upon users locking CYF and are burned as the lock time decreases.

### Staking

Users can lock CYF to obtain veCYF, period from 2 weeks to 4 years. The locked-staking is time-weighted, so longer time locks will be allocated with more distributed veCYF.

1 CYF locked for 2 weeks = 0.009589 veCYF

1 CYF locked for 1 month = 0.020548 veCYF

1 CYF locked for 1 year = 0.25 veCYF

1 CYF locked for 4 years = 1 veCYF


---

# 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://cyelefi.gitbook.io/cyclefi-protocol/tokenomics/cyf-token.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.
