> For the complete documentation index, see [llms.txt](https://docs.yieldyak.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yieldyak.com/for-farmers/pool.md). # Why use Yield Yak? ## Save Time, Gas Costs, and Earn More Yield Many DeFi protocols pay rewards to users in the form of tokens (farming rewards). Farmers who claim rewards often and compound their deposits maximise their rewards and farming yield. However, most farmers do not reach an optimal level of returns for two reasons: * **Prohibitive gas costs** to claim and compound farming rewards * **High time commitment** to frequently compound Yield Yak helps all farmers earn more yield by pooling assets and socializing the costs of compounding. This means much more frequent compounding, which happens automatically. ## Reduce Variance on Reward Asset Prices Popular Yield Yak farms compound every few hours. Reward tokens are converted into deposit tokens on behalf of all users in the pool many times per day, providing users with a blended price exposure to reward assets. Consider an example: A farmer stakes $50 of LP tokens into a farm. The farmer receives rewards worth 0.05 USDC per day. That means, on average, the farmer only generates enough value from claimed rewards to pay the gas costs by waiting for days or weeks. During this period where the farmer is waiting for the rewards to be worth claiming and compounding, they are at risk of the reward asset price shifting. Farmers who use Yield Yak instead, will earn the average price for rewards over the period while enjoying compounding effects on their deposits. --- # 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.yieldyak.com/for-farmers/pool.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.