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

# Security — Audits & Bug Bounty

STON.fi security overview with links to public audits, continuous monitoring, and the active HackenProof bug bounty program

Security is fundamental to STON.fi. Below are the public audits, continuous monitoring resources, and our active bug bounty program for responsible disclosure.

## Audits and Reviews

* Trail of Bits — STON.fi TON AMM DEX v2 Security Review (Jan 2025)
  * PDF: <https://github.com/trailofbits/publications/blob/master/reviews/2025-01-stonfi-ton-amm-dex-v2-securityreview.pdf>
* Omniston escrow contracts audit — no critical issues found
  * Blog post: <https://blog.ston.fi/omniston-escrow-contracts-audited/>
  * Summary: Initial audit of Omniston’s escrow contracts completed with no critical issues found (per the STON.fi blog; reviewed by the TonTech team).
* Continuous monitoring — CertiK Skynet
  * Project page: <https://skynet.certik.com/projects/ston-fi>

## Bug Bounty

* Program: STON.fi DEX Smart Contracts v2 on HackenProof
  * Program page: <https://hackenproof.com/programs/ston-dot-fi-dex-smart-contracts-v2>
  * Notes: Public, severity-based rewards. Please submit findings via HackenProof following their responsible disclosure process and scope.
* Community highlight: Bug bounty reward announcement
  * Blog post: <https://hackenproof.com/blog/for-hackers/ston-fi-bug-bounty-reward>

If you discover a potential vulnerability, please report it through the HackenProof program above. Avoid sharing sensitive details publicly until the issue is triaged and resolved.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ston.fi/getting-started/security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.