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

# Audit Reports

Storm Trade prioritizes the safety and transparency of its smart contracts and overall protocol architecture. Below you will find the details of conducted audits.

***

## ✅ Quantstamp Audit

In April 2024, Storm Trade underwent a comprehensive smart contract audit conducted by [Quantstamp](https://quantstamp.com/), one of the leading Web3 security auditing firms.

* **Audit Scope**: Smart contracts of the Storm Trade decentralized protocol on TON.
* **Audit Result**: **No critical or high-risk vulnerabilities** were found.
* **Status**: All reported issues were either resolved or acknowledged as intended behaviors.

🔗 [**Read full audit report**](https://certificate.quantstamp.com/full/storm-trade/21e4074a-b2cb-409d-b5df-48f683d0e8f3/index.html?suid=mHoPhrZ1#scope)

***

## ✅ Internal Audit by TON.Tech

Additionally, Storm Trade's smart contracts were audited by [TON.Tech](https://ton.tech/) - a team of TON experts supported by TON Foundation and powered by TOP, focused on supporting developers building on TON Blockchain.

**The audit included the following work:**

* **Smart contract architecture analysis:** Verified the logic, inter-contract interactions, and compliance with stated functionality.
* **Security review:** Analyzed potential vulnerabilities including reentrancy, overflows, unauthorized access, and other typical smart contract risks.
* **Recommendations:** Minor observations were identified and promptly addressed by the Storm Trade team. No critical vulnerabilities were found.
* **Conclusion:** Storm Trade's smart contracts were deemed safe for use, with all auditor recommendations implemented.

🔗 [**Read full audit report**](https://static.storm.tg/audit-report.pdf)

***

🏄 *We continue to follow the best security practices and plan to conduct further audits as the protocol 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.storm.tg/introduction/auditreports.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.