# Strategies Yield farming strategies are like different recipes for baking a cake - there are countless variations, each with its own ingredients and techniques. Some common strategies include providing liquidity to decentralized finance (DeFi) platforms, staking tokens in governance protocols, or participating in liquidity mining programs. It's all about finding the right combination of risk, reward, and opportunity that aligns with your financial goals and risk tolerance. Just like in cooking, experimentation and a pinch of caution can lead to some tasty results! Strategies are a set of smart contracts created to distribute user funds into farms i.e liquidity pools, to generate the yield that Harvest compounds. Once the rewards collected by the strategy contract reaches a certain threshold enabling Harvest to reinvest them effectively, the strategy initiates the compounding process. This involves automatically claiming the rewards, exchanging them for the original assets, and then redepositing them back into the liquidity pool and farm. These strategies undergo a thorough vetting process, including code review, security review, and testing. This process is crucial to ensure safety and prevent potential manipulation, especially since these strategies interact with external protocols as components of the vaults. Additional functionalities are implemented to address and manage these risks effectively. Strategies are equipped with the capability to withdraw all funds from third-party contracts and securely hold them within the strategy. Moreover, they have the ability to pause all functions of the contract if needed. --- # Agent Instructions: 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: ``` GET https://harvesthaven.gitbook.io/harvesthaven/harvest-products/vaults/strategies.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.