> For the complete documentation index, see [llms.txt](https://ovro.gitbook.io/ovro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ovro.gitbook.io/ovro-docs/resources/risks.md). # Risks & disclaimer OVRO is an on-chain protocol. Participation involves risk and may be subject to local laws and regulations. Crypto assets can lose value. No outcome or return is guaranteed. ## Main risks * **Chance.** A raffle is a game of chance. Most tickets do not win. * **Smart contracts.** The contracts are tested but **not yet audited**. Bugs can lead to loss of funds. * **Token.** $OVRO trades freely and its price can fall to zero. Holding $OVRO grants access to raffles, not a claim on revenue, profits or assets of the protocol. * **Third parties.** OVRO depends on Robinhood Chain, Pons V2, Uniswap v4 and the drand network. Failures or changes in those systems can affect OVRO. * **Regulation.** Games of chance and crypto assets are regulated or restricted in many jurisdictions. You are responsible for making sure your participation is lawful where you live. ## Disclaimer Nothing in this documentation is financial, investment, legal or tax advice, or an offer or solicitation to buy any asset. OVRO makes no claim of regulatory compliance in any jurisdiction. Terms of use will be published after legal review. --- # 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://ovro.gitbook.io/ovro-docs/resources/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.