> For the complete documentation index, see [llms.txt](https://docs.cellana.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cellana.finance/tokenomics/protocol-tokens.md).
# Protocol Tokens
### Cellana uses a dual token model to incentivize all parties in the ecosystem:
CELL is the utility token distributed through weekly token emissions which incentivizes users to add liquidity and stake the LP tokens in protocol gauges.
### veCELL is Cellana’s governance token in the form of an NFT.
CELL holders can lock their tokens for a fixed duration in exchange for veNFT. veNFT gives holders veCELL voting power, which can be used to vote on liquidity pools and thus redirect the CELL emissions to the voted liquidity pools.
The lock duration will vary depending on users. The maximum lock-up time is up to two years as follows:
* 100 CELL locked for 2 years will receive 1 veNFT with 100 veCELL voting power
* 100 CELL locked for 1 year will receive 1 veNFT with 50 veCELL voting power
veNFTs can be merged, split, and traded on the secondary markets. Users’ voting powers diminish over time until reaching zero when lock-up time is over. Therefore, in order to maintain voting power, users must frequently re-lock their tokens, which helps enrich the Cellana ecosystem overall.
---
# 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.cellana.finance/tokenomics/protocol-tokens.md?ask=&goal=
```
`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.