# How DualDefence Audit goes

## How DualDefence Audit goes and all possible results 

As soon as DualDefence Audit starts — security researchers can start looking for bugs in the targets mentioned in the scope of the DualDefence Audit program, and submit their findings. While auditing team, the HackenProof team and the project team work together to triage all submissions by severity, to verify if there are any critical bugs reported.\
If a critical vulnerability is discovered — the reward will be cowered from the corresponding FlashPool stake.

After all reports were assessed and the time for new submissions ended, there are two ending possible:

No critical vulnerabilities were found: 

<figure><img src="/files/7qFBk8ZsV8EcEKbNYktb" alt=""><figcaption><p>DualDefence Audit without critical findings</p></figcaption></figure>

The critical vulnerability was discovered:&#x20;

<figure><img src="/files/okyK890qNLt51q9O3985" alt=""><figcaption><p>DualDefence Audit with found critical vulnerability</p></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://docs.hackenproof.com/dualdefense-audit/how-dualdefence-audit-goes.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.