> For the complete documentation index, see [llms.txt](https://www.aevo.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aevo.xyz/docs/aevo-governance/governance/new-governance-portal.md). # New Governance Portal A comprehensive Governance Portal will be developed and maintained as the primary interface for all Aevonomics information. The dashboard will serve as both a transparency tool and a marketing anchor for protocol awareness. Among the data it will display: #### Burned Supply Tracker * Real-time display of total $AEVO permanently removed from circulation * Historical burn event data #### Staked Supply Metrics * Total $AEVO currently staked across all tiers * Percentage of circulating supply represented by staked holdings #### DAO Treasury LP Positions * Current value and composition of Uniswap V3 positions #### Volume Threshold Progress * Monthly tracker showing current exchange volumes #### Buyback Progression * Current month's volumes and corresponding buyback tier status * Historical buyback data #### Staking Rewards Distribution * Metrics and distribution details for staking rewards #### Lottery Statistics * Key statistics and outcomes for protocol lotteries --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.aevo.xyz/docs/aevo-governance/governance/new-governance-portal.md?ask=&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 `build a script that syncs our docs to a CMS` 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.