> For the complete documentation index, see [llms.txt](https://team-race.gitbook.io/race-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://team-race.gitbook.io/race-protocol/race-research/security-audit-report/findings/smart-contract-security.md).

# Smart Contract Security

This section assesses the security of the Race Protocol smart contract, focusing on access control, asset management, vulnerability resistance, and the implementation of key features like the mental poker algorithm and recipient accounts. The audit also evaluates the use of best practices and the alignment of functionality with intended behavior.

**Findings:**

{% hint style="warning" %}
This section of report is currently only accessible to the core team for security reasons. \
Once the identified issues are resolved they will be publicly revealed. 
{% endhint %}

**Best Practices:**

* The contract generally follows best practices for smart contract development, such as using established libraries and frameworks.
* However, there are opportunities for further improvement, such as adding more comprehensive unit tests and using formal verification tools to increase confidence in the contract's correctness and security.

**Functionality Alignment:**

* The contract's functionality appears to align with the intended behavior as described in the documentation.
* However, further testing and review are recommended to ensure that all instructions and functions operate as expected under various conditions and edge cases.

**Prioritization:**

* Addressing the critical and high-severity findings should be prioritized due to their potential for financial loss or gameplay disruption.
* The medium and low-severity findings should also be addressed to improve the overall security and clarity of the contract.


---

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