> For the complete documentation index, see [llms.txt](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/13-risk-factors-and-disclaimers.md).

# 13 Risk Factors and Disclaimers

EOSI Finance is an experimental, semi-open‑source project. Participation involves significant risk. Participants should carefully review the complete disclaimer and consult professional advisors. This section summarises some of the most critical considerations, including but not limited to:

1. **Regulatory Uncertainty:** DeFi, DeFAI and AI‑powered trading may fall under securities, derivatives or financial services regulations in different jurisdictions. Regulatory changes could restrict or prohibit aspects of the platform, impacting token value and services. EOSI Finance may forced due to modify or restrict features in certain jurisdictions.
2. **Technology Risks:** smart contracts and AI models can contain vulnerabilities or bugs. Despite audits, there is no guarantee of absolute security. Hacks, exploits or AI malfunctions could result in loss of funds.
3. **Market Risks:** cryptocurrency markets and prop firm trading are volatile; token values can fluctuate significantly. Trading strategies, including those executed by StandR Bot or AI agents, may incur losses. Users should invest only what they can afford to lose. There is no guarantee of profit, and you may lose some or all of your capital.
4. **Model Risk and Bias:** AI models may produce erroneous outputs due to incorrect data, overfitting or adversarial manipulation. EOSI Finance might try to mitigate this through ensemble models, human oversight and continuous retraining but cannot eliminate all errors.
5. **Counterparty and Oracle Risk:** RWA tokens rely on issuers and custodians. Failure of an issuer or a depegging event could affect asset value. Oracle failures could deliver incorrect price feeds, leading to improper liquidations or trades.
6. **Competition and Market Adoption:** the DeFi and prop firm landscape is competitive. Similar projects could emerge, offering alternative features. Success depends on user adoption, partnerships and continuous innovation.
7. **User Responsibility:** ultimately, users are responsible for understanding and managing their own risk. Participation in the presale, staking, trading or using StandR Bot is voluntary. EOSI Finance and its affiliates cannot be held liable for losses.

In summary, participation in EOSI Finance involves significant risks, including smart‑contract vulnerabilities, market volatility, liquidity shortages and potential regulatory changes. LPs may lose some or all of their deposited assets despite the protective measures. Traders are responsible for their own strategies, and past performance does not guarantee future results.


---

# 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://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/13-risk-factors-and-disclaimers.md?ask=<question>&goal=<endgoal>
```

`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.