> For the complete documentation index, see [llms.txt](https://fordex.gitbook.io/fordex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fordex.gitbook.io/fordex/security-risk-warnings/audits.md).

# Audits

## Audits

Fordex is committed to **security-first development**. External audits are a critical part of this process.

#### **Audit Strategy**

* ✅ **Smart Contract Audits** → All $FDX-related contracts and Fordex smart modules audited by reputable firms.
* ✅ **Infrastructure Audits** → Node, API, and backend reviewed for stability and data integrity.
* ✅ **Continuous Monitoring** → Automated tools to detect suspicious contract interactions or RPC failures.

#### **Audit Partners (Planned)**

* CertiK
* PeckShield
* Hacken
* Trail of Bits

#### **Why It Matters**

Independent audits provide third-party assurance that Fordex’s systems are:

* Free from critical vulnerabilities.
* Reliable for both retail and professional traders.
* Transparent about identified risks and fixe


---

# 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://fordex.gitbook.io/fordex/security-risk-warnings/audits.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.