# Protocol Revenue ## Protocol Revenue An important part of any project is the ability to sustain it's costs. We have put a good amount of thought into making sure that the development team, and community has a sustainable source of revenue. ### Swap Fees All trading fees from liquidity pools that don't have gauges will be sent to the `tank`. Once a gauge is created for a particular pool, this feature is disabled. These fees will be used at the discretion of the team to do various things, ie. KUSv3 token buybacks and burns, bribe various core pools, cover protocol and development costs. ### Protocol Owned Voting Power (POVP) The voting power of protocol will be used to vote on various pool, but dominantly on `KUSv3:WKCS` or any core `KUSv3` pool. Bribes collected via voting on the `KUSv3` pools will be used to deepen Protocol Owned Liquidity. ### Protocol Owned Liquidity The `KUSv3` rewards collected on `KUSv3:WKCS` will be fully locked to increase the POVP. ### Team Emissions As per the proposed migration proposal, 9% of the emissions are sent to the treasury. These `KUSv3` tokens will be used for various things at the discretion of the team to do various things, ie. `KUSv3` token buybacks and burns, bribe various core pools, cover protocol and development costs, add to team member voting power. ### Team Voting Each team member has their own personal `veKUS` and they can vote as they please to attempt to generate their own source of income. --- # 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://v3docs.kuswap.finance/protocol-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.