# SugarYield Audits Report

DeFi is a dangerous place. On every chain, insecure protocols bleed money due to greed, ignorance, or just pure chance. According to the[ Rekt leaderboard](https://rekt.news/leaderboard/), over $2B has been taken by hackers since the start of 2021. But it doesn’t have to be that way. At SugarYield, security is one of our core principles. SugarYield uses both DeFi-native and traditional cybersecurity techniques to ensure that vaults are a world-class DeFi product.

SugarYield Contract Audit Report: <https://drive.google.com/file/d/1tr4GONYx1B9278wKnSY_xcAeRsa4-H9N/view?usp=share_link>

Vault Factory Contract Audit Report: <https://drive.google.com/file/d/1P9Wu49QCofvCIMaVSfkh_YM8OEa3wGM_/view?usp=sharing>

Controller Contract Audit Report: <https://drive.google.com/file/d/1MmaAPxcZ_FAvY9CnzR7YaV7Z7-SJOWYS/view?usp=sharing>

Reward Factory Audit Report: <https://testnet.bscscan.com/address/0xf846a2b1a594Bf3D6096Da2b9AE63c220eEAC846#code>

<figure><img src="/files/X0Xdj1knIATOEpF02fii" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://sugar-yield.gitbook.io/sugaryield/learn-more/sugaryield-audits-report.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
