# Audits

Auditing serve as a critical checkpoint for blockchain projects, providing external validation of the protocol's security and functionality. At Inverter Protocol, we view audits not as a mere formality but as an essential component of our commitment to transparency and security.

### Multilayered Audit Approach

Recognizing the diverse nature of potential vulnerabilities, we employ a multi-layered audit strategy that starts with engaging professional auditing firms and solo researchers to regularly review our code, then hosting regular public audit competitions tap into the collective wisdom of the community, and having a continuous bug bounty pool offer a clear path for white hats to report discovered vulnerabilities.

* **In-development review:** Early bug detection through regular security reviews with our auditing partners Team Omega.
* **Pre-release audit:** Comprehensive auditing before any deployment, including a public audit competition and dedicated industry leading auditing teams.
* **Periodic and Post-Update Audits** We schedule regular audits to maintain security integrity as the protocol evolves with every new module, significant updates (major version), or additions to the core protocol.

### Security Reviews

Code security is not a one-time achievement but an ongoing task. As such, we subject our code to a continuous auditing through a concept of Security Reviews, done by [Team Omega](https://teamomega.eth.limo/):

* <https://github.com/InverterNetwork/contracts/pull/350>
* <https://github.com/InverterNetwork/contracts/pull/426>

### Dedicated Audits

#### 0xMacro Audit

* **Socials**: [Website](https://0xmacro.com/), [X](https://x.com/0xMacroSecurity)
* **Final Report Date**: July 19th, 2024
* **Protocol Version**: Inverter Protocol V1 pre-release
* **Final Audit Report**: [Inverter Github](https://github.com/InverterNetwork/contracts/blob/main/audits/2024-06-19-macro.pdf) - [O*riginal*](https://kolektivo.gitbook.io/kolektivo-docs/introduction/the-kolektivo-framework)

#### Hats Finance Public Audit

* **Contact Information:** [Website](https://hats.finance/), [X](https://x.com/HatsFinance)
* **Final Report Date**: August 12th, 2024
* **Protocol Version**: Inverter Protocol V1 pre-release
* **Final Audit Report**: [Inverter Github](https://github.com/hats-finance/Inverter-Network-0xe47e52c4fea05e555920f1dcdcc6fb8eca103eeb/blob/main/report.md) - [Original](https://github.com/InverterNetwork/contracts/blob/main/audits/2024-08-12-hats.pdf)

#### Omega Contract Audit: FM\_DepositVault\_v1

* **Contact Information:** [Website](https://teamomega.eth.limo/), [X](https://x.com/OmegaAudits)
* **Final Report Date:** July 29th, 2024
* **Protocol Version:** Inverter Protocol V1 pre-release
* **Final Audit Report:** [Inverter Github](https://github.com/InverterNetwork/contracts/blob/main/audits/2024-07-29-team-omega-issuance-token.pdf)

\----------------------------------------

For further details on our security practices and how we handle specific scenarios, please visit our [Security Guidelines](/contracts/security-guidelines.md).


---

# 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://docs.inverter.network/concepts/protocol-concepts/security/audits.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.