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

# Risks

Although we try to minimise risk, any DeFi protocol carries risk. Here are some potential risks involved with Zelo.

### Contract Risk

Despite multiple security measures, smart contracts might contain vulnerabilities or logic errors undiscovered during the development and testing phases.

### Oracle Manipulation Risk

The protocol's reliance on external oracles (e.g., Pyth, Switchboard) for price feeds introduces a risk if these oracles are manipulated or provide inaccurate data. This could affect the fairness in determining winners or the correct allocation of staking yields.

### Regulatory Risk

The regulatory environment for DeFi and cryptocurrency is evolving. Changes in regulation could impact the operation or legality of the Zelo Protocol in different regions of the world.

### Market Risk

The value of SOL and jitoSOL could be highly volatile, affecting the staked value and rewards. Extreme market movements could impact the protocol.


---

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

```
GET https://blocksmithlabs-1.gitbook.io/zelo-docs/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.