# Security

Prior to launch, re.al has undergone extensive auditing to ensure the security of contracts and safety of funds migrated to the chain.

The first was a private round of audits completed by the auditing firm Omniscia.

The second being a public round completed by the auditing firm Hacken.

Additional audits will continue to be added over time to demonstrate our continued focus on security and the reliability of the chain and protocol contracts.&#x20;

<table><thead><tr><th width="458">Audit (Issuer - Product)</th><th>Date Posted</th></tr></thead><tbody><tr><td><a href="https://drive.google.com/file/d/1uPZz9oKAsbLZbV_JzejL7hD3opyGWdKT/view?usp=sharing">Hacken - re.al DAI (plus ERC-20 bridge)</a></td><td>May 2, 2024</td></tr><tr><td><a href="https://drive.google.com/file/d/1UMYLKF1_vyEshz64limENYOTwykWk0d_/view?usp=sharing">Hacken - reETH and RWA (plus Native Bridge)</a></td><td>May 24, 2024</td></tr></tbody></table>


---

# 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.re.al/re.al-chain/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.
