> For the complete documentation index, see [llms.txt](https://docs.yo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yo.xyz/protocol/risks/insure-yousd-with-opencover.md). # Insure yoUSD with OpenCover Risk-conscious users can hold yoUSD through an OpenCover Covered Vault to protect their position against DeFi risks. Coverage begins automatically when you deposit and ends when you withdraw, with the premium streamed continuously from your yield. There is no upfront cost and no lock-in. Cover is provided through OpenCover, with claims managed end-to-end. 🔗 Get covered → [opencover.com/vaults/yo](https://opencover.com/vaults/yo) ### ⚙️ How it Works When you deposit into the Covered yoUSD vault, your position is automatically insured for as long as you hold it. No Signup, No Upfront Cost: The cover premium is streamed continuously from the vault's yield, meaning you earn a slightly lower net APY in exchange for peace of mind. Full Flexibility: You can withdraw at any time; coverage ends exactly when your position does. Hands-off Claims: If a covered loss event occurs, OpenCover manages the claim and payout process end-to-end. ### 🛡 What's Covered The Covered yoUSD vault protects deposits against core DeFi risks affecting the yoUSD strategy and its underlying lending markets, including: * Smart Contract Exploits: Loss of funds due to a bug or vulnerability in the covered contracts. * Oracle Failure & Manipulation: Faulty price feeds or deliberate price manipulation leading to loss. * Liquidation Failure / Bad Debt: Failure of liquidations to clear positions correctly, resulting in socialized bad debt. * Governance Attacks: A malicious upgrade forced through an on-chain governance mechanism. Standard exclusions apply, including phishing, private key compromise, and normal market price movements. Check the Cover Terms for the full list. ### 📊 Coverage Scope & Sublimits Coverage is subject to per-component sublimits, meaning the maximum payout attributable to any single underlying market is capped as a percentage of your Cover Amount: **Yo Protocol: Up to 70% of the Cover Amount** Each Underlying Morpho Market: Up to 70% of the Cover Amount (e.g., cbBTC/USDC, WETH/USDC, wstETH/USDC, cbETH/USDC across Base and Ethereum) **OpenCover Covered Vault: Up to 100% of the Cover Amount** A 4% deductible of the Cover Amount applies to all claims. Sublimits and deductibles are defined in the Annex. ### 📋 Key Details & Reference * Covered Asset: yoUSD * Covered Vault (Base): 0x428dEDa4f7A026d62A4eb93C856DB9AEB7Ea92d3 * Designated yoUSD Vault (Base): 0x0000000f2eb9f69274678c76222b35eec7588a65 * Deductible: 4% of Cover Amount * Upfront Cost: None (premium streams from yield) * Duration: None (runs from deposit to withdrawal) * Claims: Managed end-to-end by OpenCover ### 🔗 Canonical Links Reference UI / Get Covered → Cover Terms (Policy) → Annex (yoUSD-specific) → --- # 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.yo.xyz/protocol/risks/insure-yousd-with-opencover.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.