# 5.1 Revenue The protocol fees listed below are up for change as the VEME DAO sees fit and proposals move through **VeFi Protocol** 32% of all VEME being minted by liquidity through bonding mechanisms (DAI, MATIC, etc), goes into the VEME DAO treasury. This is an actively ongoing process. **Voltage Protocol** Voltage takes 5% of an NFT sold through Voltage, burns 2.5%, and sends the other 2.5% to the VEME DAO’s treasury to fund further advancements on the tech stack. Apart from minting, Voltage also allows for licensing, advertising, and streaming content. Fees have to be determined on this, but will have a similar effect on the deflationary nature of burning tokens. Part of the fees generated will be added to the treasury to fund further enhancements on the tech stack. **AINI - The DAO Launchpad** Every time a V/ DAO is funded, part of its treasury will be bonded inside of the Vefi protocol to generate sticky liquidity. This provides both a source of funding for the V/DAO as well as a source of revenue for the VEME DAO through distributions. A % of all V/DAO tokens will be stored in the VEME DAO treasury, and the VEME DAO as a unit will be able to directly invest into its own DAOs. This is a mutually reciprocal relationship in which all tides rise together. The model is still under construction; fee mechanisms are under discussion. **DAPPS** Veme is built to have an ecosystem of DAPPS plug into its main model, giving a % of revenue from its operation into the VEME Dao itself. Our first DAPP is an asynchronous video communication ‘slack’ for DAOs. --- # 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://veme-master.gitbook.io/dao/5.-finance/5.1-revenue.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.