# Risks

While no protocol is entirely risk-free, the Fusion infrastructure has implemented [extensive measures](/fusion-for-liquidity-providers/user-guide/depositing/vault-security-considerations.md) to minimize potential issues. The protocol's code is publicly available, has undergone multiple smart contract [audits](/fusion-for-liquidity-providers/why-fusion/security-features.md#audits), and is subject to an ongoing bug bounty campaign and specialized technical reviews.

Key risk categories and their corresponding mitigation strategies are detailed below. For more in-depth information, refer to the risk framework and security and audits sections.

| Risk Category       | Description                                                                                                                                                                                                                                                                                                    | Mitigation Strategy                                                                                                                                                                                                   |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Smart Contract Risk | Potential for bugs or vulnerabilities in the Fusion Protocol code or underlying reserve tokens.                                                                                                                                                                                                                | Audits and Governance: Code is public, audited by multiple firms, and any changes require thorough vetting and community approval via onchain governance. An ongoing bug bounty program is also in place.             |
| Oracle Risk         | Reliance on third-party data providers (oracles) for price feeds and other external data (e.g., liquid staking token redemption ratios). A compromised or failed oracle could lead to incorrect asset valuations.                                                                                              | Decentralized Oracles: Uses robust, tamper-resistant decentralized oracle solutions, such as Chainlink, for reliable data feeds.                                                                                      |
| Strategy Risk       | Inherent in DeFi vaults, involving potential losses from the failure of underlying investment strategies defined by Atomists. This includes poorly performing strategies, improper asset management, and external risks from interacting with other protocols (e.g., impermanent loss, liquidation, exploits). | Transparency and Oversight: All Atomist-defined investment strategies are publicly visible, allowing for continuous scrutiny by the community, security experts, and contributors.                                    |
| Network Risk        | Issues related to the underlying blockchain networks on which Fusion operates, such as congestion, censorship, or security vulnerabilities.                                                                                                                                                                    | Robust Onboarding Framework: Fusion Governance employs a rigorous network onboarding framework to vet new networks before integration, with all integration decisions overseen by community-based onchain governance. |


---

# Agent Instructions: 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:

```
GET https://docs.ipor.io/fusion-for-liquidity-providers/user-guide/risks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.