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

# Security

We place the highest priority on the security of each of our products. We understand the protocol's complexity, the challenges of releasing bug-free software, and the responsibilities of maintaining a value-bearing protocol. As a result, we've gone to great lengths to ensure that the smart contracts and overall deployment have been thoroughly reviewed by top security and audit firms, as well as internally scrutinized line by line.\\

We've worked with renowned audit organizations like BlockSec, Zokyo, and TechRate to audit every smart contract that the Propel tech team creates. Furthermore, Propel's QA guarantees that each product delivered is of the highest quality, ensuring that our partners do not suffer any security difficulties.

Check out the audit reports in the section ahead.


---

# 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.propel.xyz/protocol/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.
