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

# Risks Overview

### Smart Contract Risk

While Hypertrade smart contracts are designed with security in mind and undergo audits, no smart contract can be guaranteed to be completely free of vulnerabilities. Users should only deposit funds they can afford to lose.

### Impermanent Loss

Liquidity providers are exposed to impermanent loss when the price ratio of deposited tokens changes compared to when they were deposited. This is especially relevant for v3 concentrated liquidity positions with narrow price ranges.

### Slippage Risk

Large trades relative to pool liquidity may experience significant slippage. Always check the expected output amount and price impact before confirming a swap.

### Market Risk

Token prices can be volatile. The value of your assets may decrease significantly in a short period of time.


---

# 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://docs.ht.xyz/risks/risks-overview.md?ask=<question>&goal=<user_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.
