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

# Testing & Validation

Reliability is central to Liquidex. The smart contracts have been rigorously tested to ensure safe execution under **live market conditions**.

***

## Tested against real markets

Rather than relying on simplified or synthetic test environments, the contracts were validated on **mainnet forks** using **real data**:

| Test asset                | Why it matters                                        |
| ------------------------- | ----------------------------------------------------- |
| **Real stock tokens**     | Actual tokenized assets (e.g. `NVDA`, `AAPL`, `MSFT`) |
| **Real Uniswap V3 pools** | Genuine liquidity pools on the Robinhood Chain        |
| **Real Chainlink feeds**  | Actual decentralized price oracles                    |

{% hint style="info" %}
By testing against **real tokens, real pools, and real feeds**, the protocol verifies its logic behaves correctly under the exact conditions it will face in production.
{% endhint %}

***

## Why this matters for you

Testing against live market infrastructure means the protocol's core mechanics — **deposits, withdrawals, scoring, and rebalancing** — have been exercised in realistic conditions:

* Reduced risk of unexpected behavior
* Greater confidence in core functionality
* Proven execution with your capital at stake

{% hint style="success" %}
**Tested where it matters.** When you invest, you benefit from a protocol validated against the real world.
{% endhint %}


---

# 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.liquidex.sh/transparency-security/testing-and-validation.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.