> For the complete documentation index, see [llms.txt](https://basofinance.gitbook.io/basofinance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://basofinance.gitbook.io/basofinance/tokenomics/gauges-and-rewards.md). # Gauges & Rewards ### Gauge Voting $veBASO holders decide which liquidity pools receive emissions in a given epoch by voting on their preferred liquidity pool gauges. $BASO emissions will be distributed proportionally to the total votes a liquidity pool receives. ### Rewards There are 4 types of rewards on Baso Finance: Emissions, Fees, Bribes, and Rebases. ### Rewards claim Details for reward claim can be found in the ### Whitelisting While Baso supports permissionless liquidity pool and gauge creation, these can only include whitelisted tokens. The protocol will launch with an extensive list of pre-whitelisted tokens, including those from partner protocols. ### Commissaire Requirements for whitelisting are critical to ensuring that the protocol cannot be exploited by actors attempting to game emissions. To support the health of the protocol and ecosystem, the Commissaire (a Curve-esque Emergency DAO) will have the right to disable hostile gauges. The Commissaire will initially consist of seven members from the Baso team and prominent figures from within the Optimism community. --- # 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://basofinance.gitbook.io/basofinance/tokenomics/gauges-and-rewards.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.