> For the complete documentation index, see [llms.txt](https://docs.campiexyz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.campiexyz.io/campie-maximizing-benefits.md). # Campie Maximizing benefits ## **What is Campie?** Campie is a groundbreaking SubDAO, created by Magpie, that is dedicated to supporting the long-term development of Camelot Exchange. Built under the principles of Camelot’s design, it amplifies the platform’s central functionalities. The primary focus of Campie is to lock GRAIL tokens as xGRAIL, which provides access to numerous benefits within the Camelot Ecosystem. Thanks to this approach, the platform is able to offer enhanced rewards for liquidity providers, cost-effective governance power for Camelot voters, and the opportunity for GRAIL holders to earn rewards for their active participation without any mandatory lock-up period. ## How does Campie support Camelot DEX? * Boosted rewards for GRAIL holders * Boosted yields for Liquidity Providers * Cost-Effective Voting Power & active user engagement rewards for Camelot DEX Voters (Real Yield) * Decreasing GRAIL circulating supply * Providing a platform accessible to a wide range of users. --- # 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://docs.campiexyz.io/campie-maximizing-benefits.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.