# Security Audit Report

Dated March, 2024 an independed security audit of RACE Protocol was conducted to identify potential issues and vulnerabilities to be addressed. 

Some parts of the final report are temporarily private to exclude unnecessary external tampering while the team addresses identified issues. Once the identified potential issues and vulnerabilities are resolved, they will become publicly available. 

{% content-ref url="/pages/X2V2V7Rw1sAJ2wCkXQlb" %}
[Executive summary](/race-protocol/race-research/security-audit-report/executive-summary.md)
{% endcontent-ref %}

{% content-ref url="/pages/4SLwylkhOBGt6hk4y14f" %}
[Findings](/race-protocol/race-research/security-audit-report/findings.md)
{% endcontent-ref %}

{% content-ref url="/pages/upBlbdUqunEuhMPBdsZ6" %}
[Recommendations](/race-protocol/race-research/security-audit-report/recommendations.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ti4Jp6io8wii0rjwRaVL" %}
[Conclusion](/race-protocol/race-research/security-audit-report/conclusion.md)
{% endcontent-ref %}


---

# 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://team-race.gitbook.io/race-protocol/race-research/security-audit-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.