> 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/server-side-security.md).

# Server-side Security

This section analyzes the Transactor and validator server implementations for potential vulnerabilities in communication, data handling, and the P2P randomization process. It also reviews server-side security measures for protecting game state and player assets.

**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 %}

**P2P Randomization Security:**

* The P2P randomization process appears to be designed securely, utilizing a variant of the mental poker algorithm.
* However, further analysis and testing are recommended to ensure its resistance to manipulation and collusion attacks by potentially malicious servers.

**Server-side Security Measures:**

* The codebase does not explicitly show robust server-side security measures for protecting game state and player assets.
* It is recommended to implement additional security practices, such as secure storage of secret keys, access control mechanisms, and intrusion detection systems, to further protect the server environment and sensitive data.


---

# 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:

```
GET https://team-race.gitbook.io/race-protocol/race-research/security-audit-report/findings/server-side-security.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.