> For the complete documentation index, see [llms.txt](https://docs.aozo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aozo.io/aozo-earn/risks-and-security/key-risks.md). # Key risks Risks to consider before using AOZO Earn. {% hint style="warning" %} AOZO Earn is not a bank deposit. Digital assets can lose value. You may lose some or all of what you deposit. {% endhint %} AOZO Earn involves: * Strategy and market risk * Liquidity constraints and valuation uncertainty * Counterparty and smart-contract risk A strategy position may not be withdrawable for its displayed value or when you request it. ### Losses and outstanding withdrawals In a severe shortfall, product design documents include recovery measures. These may include adding capital and, when applicable conditions are met, reducing eligible unsettled withdrawal amounts. This is a loss-allocation measure. It is not a normal withdrawal feature. It does not promise that losses will be fully covered. Exact conditions and treatment depend on the final product terms. The junior pool, if enabled, is designed to absorb eligible economic losses before losses reach the main depositor position. Its limits and exclusions appear in [Portfolio composition](/aozo-earn/transparency/portfolio-composition.md). It does not remove the possibility of loss to either group. ### Before you use AOZO Earn Verify supported networks, contract addresses, availability, fees, withdrawal terms, and risk information through official AOZO channels. See [Security information](/aozo-earn/risks-and-security/security-information.md) for security guidance. Read [Liquidity and withdrawals](/aozo-earn/transparency/liquidity-and-withdrawals.md) and [Governance and controls](/aozo-earn/transparency/governance-and-controls.md) for related information. --- # 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.aozo.io/aozo-earn/risks-and-security/key-risks.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.