> For the complete documentation index, see [llms.txt](https://avanatoken.gitbook.io/avana-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avanatoken.gitbook.io/avana-project/avana-whitepaper/avana-utility-token.md).

# AVANA Utility Token

AVANA's ecosystem is built on a token economy, where the AVANA utility token ($AVAN) is used to reward creators for their work and to incentivize community members to participate in the platform. Creators can earn $AVAN through a variety of ways, such as by creating and publishing content, engaging with their audience, and participating in community governance. Community members can also earn $AVAN by supporting their favorite creators, curating content, and participating in community governance.

**Avana’s native token is an BEP-20 token with the following specs:**

* Symbol - $AVAN
* Type - BEP-20
* Initial Circulation Supply - 25,200,000
* Max Supply - 1,000,000,000 AVN tokens
* Coin Type - Utility Token
* NO MINTING


---

# 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:

```
GET https://avanatoken.gitbook.io/avana-project/avana-whitepaper/avana-utility-token.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.