> For the complete documentation index, see [llms.txt](https://polywhale.gitbook.io/oldywhale/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polywhale.gitbook.io/oldywhale/yield-aggregator/leveraged-farming-1.md). # 👨‍🌾 Leveraged Yield Farming ![](/files/-MZoWcks8tCWrDrD9cIg) \ Leveraged Yield --------------- Polywhale will be the first leveraged yield farm on Polygon (Matic). ETH/MATIC lenders will be able to earn high interest on ETH/MATIC. The lending interest rate comes from leveraged yield farmers/liquidity providers borrowing these ETH/MATIC to yield farm/provide liquidity. Yield farmers can get even higher farming APY and trading fees APY from taking on leveraged yield farming positions. By taking leverage, the protocol would borrow ETH/MATIC on users' behalf to yield farm. ## How it's done Liquidity providers can get even higher trading fees APY from taking on leveraged liquidity providing positions. By taking leverage, it would borrow ETH/MATIC on users' behalf to provide liquidity. \ \ For leveraged yield farming pools (all pools under Yield Farming Pools section that support more than 1x leverage), the APY comes from yield farming APY on leverage + trading fees APY on leverage. This implementation will automatically reinvest the farmed tokens for leveraged yield farmers.\ \ **All of the APY earned will be accrued to the position value. Additionally, as a part of our emissions, all the leveraged positions of more than 1x will also get KRILL on top.** A part of the users will be able to contribute to single staking pools with MATIC and ETH. Those pools will be utilised to leverage yield positions across the entire network. --- # 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://polywhale.gitbook.io/oldywhale/yield-aggregator/leveraged-farming-1.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.