> For the complete documentation index, see [llms.txt](https://docs.liquify.ventures/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquify.ventures/audited-smart-contracts/our-commitment-to-security.md).

# Our Commitment to Security

**We value your funds like ours, so security isn’t an afterthought — it’s at the core of everything we build.**

#### ✅ Audited & Battle-Tested

Liquify’s core smart contracts have undergone **3 independent audits** and a **public audit contest**, bringing in insights from some of the sharpest minds in the ecosystem.

In total, **more than 15 security experts** have reviewed our code across audits, internal reviews, and open competitions.

#### 🔒 Security by Design — Even in Tokenomics

We’ve baked security into our long-term roadmap. **2% of the $LQFY token supply** is reserved exclusively for **a permanent bug bounty fund** — incentivizing responsible disclosures and keeping Liquify secure as it evolves.


---

# 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.liquify.ventures/audited-smart-contracts/our-commitment-to-security.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.