> For the complete documentation index, see [llms.txt](https://docs.osero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.osero.com/osero-app/yield+-vaults/risks-specific-to-yield+.md). # Risks Specific To Yield+ Yield+ carries the same risks that apply to Savings, including smart contract, stablecoin and market, liquidity, cross-chain, and wallet risks. ### Risks introduced by leverage #### Liquidation risk If LTV rises too quickly for the strategy to deleverage, the position could approach or reach the liquidation threshold in the underlying Morpho market. #### Negative spread risk If borrowing costs rise above the Sky Savings Rate, the strategy reduces leverage toward 1x. As a result, Net APY can decrease significantly. #### Withdrawal timing risk Withdrawals are not instant. Larger requests may take longer because the strategy needs time to unwind leverage. #### Market-specific risk Changes in liquidity, utilization, or oracle conditions in the Morpho markets can directly affect the position. #### Vault infrastructure risk Yield+ relies on Aera V3 and Morpho Blue in addition to Sky’s sUSDS infrastructure. Each introduces its own smart contract and protocol risks. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.osero.com/osero-app/yield+-vaults/risks-specific-to-yield+.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.