> For the complete documentation index, see [llms.txt](https://stabilize-2.gitbook.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stabilize-2.gitbook.io/start/stabilize/audits-security-risks-team.md).

# Audits, Security, Risks, Team

## Audits

The Stabilize protocol has been audited by:

Bramah Systems - [Audit Link](https://bramah.systems/audits/Stabilize_Finance_Audit_Bramah.pdf)

Defiyield.Info - [Audit Link](https://safefiles.defiyield.info/safe/files/audit/pdf/Security_Audit_for_Stabilize_finance.pdf)

Please keep in mind these audits were performed at a snapshot in time and the protocol has built upon the audited code.

### Security

The development team takes security very seriously. The team continually dedicates a portion of the treasury funds for smart contract reviews and audits. The Stabilize development team has relinquished direct control over minting the Stabilize reward tokens. The emissions operator contract controls the minting rate. In addition, all governance functions are controlled by a 24 hour time-lock. This gives depositors enough time to make a decision to stay in the protocol or not.

### Risks

Stabilize protocol incurs risk just like all token protocols do. If one of the pooled tokens collapse and doesn't recover, you may realize losses. There are also unknown smart contract risks. The general rule is, do not deposit more than you are willing to lose.

Further, if you supply liquidity to the STBZ/ETH or STBB/BNB pool, you are exposed to the risk of impermanent loss (IL).

### Team

We are an anonymous team. This is to assure that development can remain decentralized and developers can be free from targeting.


---

# 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://stabilize-2.gitbook.io/start/stabilize/audits-security-risks-team.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.