# 3 - Tokenomics

## New Treasury Organisation

$AEVO does not come from nowhere, being a rebrand of our previous governance token $RBN, as voted in Ribbon Finance's latest governance proposal, RGP-33. This implies that the distribution of the token in large part cannot be changed, $RBN being widely distributed in the market and allocated.

However, the holder of the largest number of tokens is the DAO Treasury and this capital, has always been unproductive, except for that used in the liquidity pools supporting $RBN.

With AGP-1 we propose a more dynamic and functional allocation of Treasury, which will be converted to $AEVO at TGE. This new organisation is linked to the genesis of the Committees, which will have the task of administering the sums.

We propose a fixed breakdown of the 45% of $RBN that the DAO owns in the following way:

* Up to 16% of $AEVO for Incentives (Airdrop Included), managed by the [Growth & Marketing Committee](/approved-proposals/agp-1-aevo-governance/2-governance/committees/growth-and-marketing-committee.md). These tokens will be used in initiatives to disseminate the Governance token and attract more users/liquidity to the platform.
* Up to 9% of $AEVO for Token Liquidity, managed by the [Treasury and Revenues Management Committee](/approved-proposals/agp-1-aevo-governance/2-governance/committees/treasury-and-revenues-management-committee.md). These tokens will be used by the Committee to support the liquidity of $AEVO on DEXes and CEXes
* Up to 5% of $AEVO for Community growth and bounties, managed by the [Growth & Marketing Committee](/approved-proposals/agp-1-aevo-governance/2-governance/committees/growth-and-marketing-committee.md). These tokens will be used for Community related events and bounties.
* 16%: unearmarked/reserved for future DAO spending. Note: The teams 2% yearly allocation will come from this portion ([see Section 2 - Operating Expenses](/approved-proposals/agp-1-aevo-governance/2-governance/aevo-revenues/operating-expenses.md))


---

# Agent Instructions: 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://agp.aevo.xyz/approved-proposals/agp-1-aevo-governance/3-tokenomics.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.