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

# Overview

<figure><img src="https://content.gitbook.com/content/n3odl4ymHi6P7lINhkcx/blobs/igIJZ79JhsitVEmIdgoJ/GRIX-for-docs.png" alt=""><figcaption><p>GRIX Token</p></figcaption></figure>

## GRIX Token

**GRIX** token serves as the utility token that fuels the Grix ecosystem, aligning incentives to boost protocol growth.

## veGRIX - Voting Escrowed GRIX

**veGRIX** token serves as the governance access token within the Grix protocol, enabling holders to actively participate in Grix Finance's future decentralized governance. It is obtained by staking native GRIX tokens with a 1:1 conversion ratio. veGRIX accrues value through three primary methods:

* **Trading Fees:** Holders receive a percentage of trading fees.
* **esGRIX Rewards:** Holders earn esGRIX rewards for their participation.
* **Market Voting:** Holders can vote to boost esGRIX incentives for specific markets.

This structure ensures that veGRIX holders are integral to the protocol's growth and decision-making processes.

## esGRIX - Escrowed GRIX

**esGRIX** is an additional reward token that is distributed to both veGRIX holders and platform traders. It serves as an incentive to encourage active participation and drive protocol growth. esGRIX can be vested to be turned into GRIX tokens.

## Fee Flow and Distribution

<figure><img src="https://content.gitbook.com/content/n3odl4ymHi6P7lINhkcx/blobs/8ZRgO0Yhpjz48hWv9tcu/Grix%20Premiums%20and%20Fees.png" alt=""><figcaption><p>Grix Distribution of Premiums an Fees</p></figcaption></figure>

Grix protocol collects fees and premiums from users trading on the platform. These fees are distributed to ensure the protocol's sustainability and incentivize active participation:

**Premiums and Fees:** Users pay premiums and fees when trading through the Grix platform.

**Fee Pool:** These fees are collected in the Fee Pool module.

**Fee Distribution:** The fees are divided into three parts:

* **Solver Fees:** These incentivize Solvers to provide optimal routing solutions.
* **Grix Stakers Fees:** These encourage holders to stake GRIX, thereby strengthening the community.
* **Protocol Fees:** These cover the transaction execution and operational costs of the Grix protocol.

## Token Address

<table><thead><tr><th width="231">Token</th><th>Token Address</th></tr></thead><tbody><tr><td>GRIX Etheruem</td><td><a href="https://etherscan.io/token/0xa150376112dd24E873086b51347EddD5F2e147D5">0xa150376112dd24E873086b51347EddD5F2e147D5</a></td></tr><tr><td>GRIX Arbitrum</td><td><a href="https://arbiscan.io/token/0x812F2D5Ff6088ed7A655567dBcDf0d42cf07ca38">0x812F2D5Ff6088ed7A655567dBcDf0d42cf07ca38</a></td></tr><tr><td>GRIX Solana (Wormhole)</td><td><a href="https://solscan.io/token/E8iWdPoeVDHJn1EHifeCAFWvKZyTN9WXrmccFEx1Hxa">E8iWdPoeVDHJn1EHifeCAFWvKZyTN9WXrmccFEx1Hxa</a></td></tr><tr><td>veGRIX</td><td>To be announced</td></tr><tr><td>esGRIX</td><td>To be announced</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.grix.finance/grix/tokenomics/overview.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 `automate deployments from our CI pipeline` 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.
