# Post AGP-3 Asset Allocation and Management AGP-3 introduced the following asset allocation: * All the remaining Treasury $RBN tokens will be converted to $AEVO at a 1:1 ratio (including the Uniswap RBN/USDC pooled ones). * 69,000,000 $AEVO (6.9% of the total supply) will be burned in an exceptional, one-off event to mark the starting point of the new Aevonomics. * 48,000,000 $AEVO will be allocated to the new Staking Rewards, managed by the Treasury and Revenues Management Committee. * 103,000,000 $AEVO will be allocated to the new Trading Rewards campaigns (including contests), managed by the Growth & Marketing Committee. * 65,722,576 $AEVO will remain unearmarked/reserved for future DAO spending. * All other available Treasury assets will be gradually converted to USDC, to be managed by the Treasury and Revenues Management Committee new multisig as needed. ## DAO Owned Liquidity The DAO Treasury will maintain all existing $AEVO Uniswap V3 liquidity positions, managed by the Treasury and Revenues Management Committee based on liquidity needs and fee generation efficiency (as established in AGP-1). The Treasury has accumulated almost 1M USDC in fees from its $AEVO Uniswap V3 positions. This capital, previously sitting idle, will now be activated: 69% of accumulated LP fees will be distributed annually (end of June, each year) to stakers through the new Staking Rewards. --- # 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/governance/dao-treasury/post-agp-3-asset-allocation-and-management.md?ask= ``` 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.