# Token Distribution

$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.

**As of 01/01/2025, $AEVO is 100% unlocked and circulating.** The largest token holder remains the [Aevo DAO Treasury](https://etherscan.io/address/0xdaeada3d210d2f45874724beea03c7d4bbd41674).

RBN holders are invited to exchange their tokens in AEVO on a 1:1 basis, directly on the Exchange. There are nor will there be any limits on amounts or deadlines. The converted RBN will be held and immobilized in the [staking contract](https://etherscan.io/address/0x38913051E01D4F6910cB66bB9aC3cb77D746Ad81), which is immutable.

## Treasury Allocation

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 the DAO approved a more dynamic and functional allocation of Treasury. 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 DAO Treasury in the following way:

* Up to 16% of $AEVO for Incentives (Airdrop Included), managed by the Growth & Marketing Committee. 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. 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. These tokens will be used for Community related events and bounties.
* 16%: unearmarked/reserved for future DAO spending. Note: The Aevo Project Contributors [2% yearly allocation](broken://pages/4eZi9wEkxLwtrvC5UllV) will come from this portion.


---

# 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://docs.aevo.xyz/aevo-governance/token-distribution.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.