> For the complete documentation index, see [llms.txt](https://ocelex.gitbook.io/ocelex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ocelex.gitbook.io/ocelex/protocol-overview/dex-functionalities/voting/vote-for-liquidity.md). # Vote for Liquidity The "Vote for Liquidity" feature enables veOCX holders to directly influence the distribution of emission rewards among various liquidity pools. This empowers token holders to guide the platform's growth by supporting pools they deem worthy, thus directly impacting Ocelex's liquidity dynamics. It offers the dual advantage of shaping the platform’s direction and earning from the trading fees of supported pools, fostering active governance engagement and aligning liquidity providers' interests with Ocelex’s success. Gauges in Ocelex serve as a mechanism to capture $veOCX holders' votes, directing emissions and rewards to chosen liquidity pools, ensuring a fair distribution of rewards and encouraging active participation. Activation of gauges necessitates token whitelisting, enabling partners to secure gauges for their ecosystem tokens following thorough evaluation. The Ocelex team may also establish gauges for key tokens like wETH and wBTC, enhancing the platform’s functionality and appeal. ### Enhancing Efficiency with Gauges Ocelex has introduced three major improvements to overcome inefficiencies observed in Solidly’s gauge system and cultivate a more effective DeFi ecosystem: * **Token Whitelisting:** Tokens must satisfy certain conditions, such as a minimum TVL of $10,000, to be eligible for gauges, ensuring the pools’ stability and value. Exceptions can be considered case by case. * **Emergency Council:** Initially comprising Ocelex core team members and eventually expanding to include community members, advisors, and DeFi experts, this council actively manages gauges with the authority to remove unproductive ones, adjust OCX emissions, and modify multisig addresses as necessary. * **Enhanced Governance:** The Council’s actions aim to ensure gauges positively affect the ecosystem's objectives and partnerships, with measures against non-compliant gauges. These efforts underscore Ocelex's commitment to a transparent, community-led, and equitable DeFi space, steering towards a more productive and just financial ecosystem. ### Partner Integration Strategy In our Genesis phase, integrating partners into the Ocelex ecosystem has been a priority, including allocating a portion of veOCX that's permanently locked for partner protocols. The distribution among potential partners will focus on shared objectives and commitments. **Future partner considerations may involve:** * Supporting essential gauges with incentives. * Token swaps to strengthen collaborations. * Collaborative integration projects for seamless interoperability. * Joint marketing initiatives to enhance visibility and growth. These criteria are tailored during negotiations to align with shared goals, maximizing benefits for all stakeholders. Our aim is to nurture a strong, thriving ecosystem collaboratively. --- # 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://ocelex.gitbook.io/ocelex/protocol-overview/dex-functionalities/voting/vote-for-liquidity.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.