> For the complete documentation index, see [llms.txt](https://v3docs.kuswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v3docs.kuswap.finance/gauges.md). # Gauges As mentioned in [Whitelisting](/whitelisting.md), in order to get an active gauge, a token requires whitelisting. Partners will all have various gauges for the tokens of their ecosystems on a token by token based consideration. ## Fees and Gauge-less LPs Trading fees from LPs that are not granted gauges are sent to the treasury. Once a gauge is produced, all fees going forward will be sent as bribe to voters. Because of this, it is recommended that projects attempt to follow [Whitelisting](/whitelisting.md). ## Future Partners At Genesis, we have whitelisted our genesis partners, however we do hold in reserve `veKUS` NFTs for future partner protocols. Negotiations with potential projects will distinguish how they can get an veNFT. That being said, some ideas of the type of requirement for future partners would be: * A requirement to bribe some gauges, their own or core. * A token swap * Integrations * Marketing campaigns --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://v3docs.kuswap.finance/gauges.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.