> For the complete documentation index, see [llms.txt](https://docs.flurry.finance/flurry-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flurry.finance/flurry-finance/security/risks.md).

# Risks

**As with any investment, there are risks associated with yield farming DeFi protocols**. 

The Flurry Protocol is no exception, and we want to be open with you about the possible risks users can incur:

{% hint style="info" %}
Flurry Protocol smart contract risk
{% endhint %}

While Flurry is undergoing audit, and will continue to stress test the protocol, it is possible for logic errors in the algorithms to occur in the smart contracts that could lead to the loss of funds for rhoToken and $FLURRY holders. 

{% hint style="danger" %}
Third-party protocol risk
{% endhint %}

The Flurry Protocol makes use of other DeFi Protocols like Compound, Aave, and C.R.E.A.M. to generate yields. These protocols themselves are open to smart contract risks, despite their longstanding position in the crypto community, good track records, and completed audits. Failures in these protocols could lead to the loss of funds for rhoToken holders. 

{% hint style="danger" %}
Stablecoin risks
{% endhint %}

While stablecoins are inherently stable, it’s important to note that they may fluctuate in value from time to time, which would result in the fluctuation of the rhoToken tied to it. Each one of the stablecoins Flurry uses has in the past had these periods of fluctuation. While rhoTokens are tied 1:1 with underlying stablecoins, it does not guarantee the backing stablecoins will maintain their value. 

## Use At Your Own Risk

With these considerations in mind, Flurry Financial advises users to use the Flurry Protocol at their own risk. And as always in the world of crypto, never deploy more than you are willing to lose.


---

# 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.flurry.finance/flurry-finance/security/risks.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.