# Audits

During the development of Flaunch we undertook three audits to ensure that the protocol is secure and functions as expected. At each audit we remediated or acknowledged all known issues.

### Audit 1: Omniscia

Omniscia undertook our initial audit. Unfortunately this cannot be shared publicly, but a synopsis extract from the findings has been provided below showing their initial findings.

<figure><img src="/files/5Ias0fkiG6rljvUdclJM" alt=""><figcaption></figcaption></figure>

### Audit 2: Enigma Dark

The first Enigma Dark audit followed on from the Omnisca findings and also reviewed some newly implemented zap logic including flaunch scheduling and premining.

{% file src="/files/A1IwxrRcuIl8XiKy4QAb" %}

### Audit 3: Enigma Dark

After the initial Enigma Dark audit there was a small raft of changes to optimise flow which were subsequently reaudited.

{% file src="/files/uhZxFlLghTHOqr9Ejotz" %}

### Audit 4: Enigma Dark

For our version 1.1 contracts, Enigma Dark followed up to audit our new and modified functionality.

{% file src="/files/Jo1O11dvAQm4GK7L2llf" %}


---

# 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.flaunch.gg/protocol/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.