# Aevo Revenues

The DAO and Apogee are successful only if Aevo is successful. They both pursue the common goal of supporting Aevo's growth financially, as it is equivalent to supporting their own growth.

Firstly, with the merger of Ribbon and Aevo, all revenues from both platforms should be consolidated. Currently, the Ribbon DOV revenues flow to the Ribbon DAO, whereas the Aevo revenues flow to the Aevo Insurance Fund. Going forward, fees from both the Exchange and Vaults will flow into a new wallet governed by the [Treasury and Revenues Management Committee](/approved-proposals/agp-1-aevo-governance/2-governance/committees/treasury-and-revenues-management-committee.md).

Secondly, Apogee has been historically funded through VC raises and has not drawn down cash from the DAO. However, to build a self-sustaining ecosystem that does not rely on constant token sales, Apogee now requests a budget from the DAO to fund the expenses of maintaining, developing, and operating Aevo.

The multisig will divide the amounts received monthly as follows:

* 25% of the top-line revenue immediately goes to Aevo's Insurance Fund, with the purpose of increasing its size (and thus supporting the growth of the exchange);
* Remaining revenue goes to paying for Operating Expenses of Apogee.
* Once that is covered, Surplus Revenue will be used to increase protocol owned liquidity of $AEVO-USDC, similar to Maker’s [Smart Burn Engine](https://forum.makerdao.com/t/introduction-of-smart-burn-engine-and-initial-parameters/21201).


---

# 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/2-governance/aevo-revenues.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.