# Audits

At Lynex, we place the utmost importance on the security and safety of our platform and community. Our approach to security is comprehensive and proactive, ensuring that every feature and integration passes through rigorous auditing and testing processes.

### **Key Security Measures at Lynex**

* **Successful Audit by Secure3:** Demonstrating our unwavering commitment to security, Lynex has successfully completed a thorough audit conducted by Secure3. [View the Audit Report.](https://app.secure3.io/en/0dba16bb)
* **Robust Codebase Heritage:** Lynex, rooted in Thena and Velodrome, and ultimately derived from Solidly's codebase, boasts a history of robust security. This lineage, validated by multiple high-level audits of Thena and an absence of reported exploits, provides a strong, secure foundation for Lynex's platform.

### **Related Security Audits and Practices**

* **Thena’s Security Audit:** Which Lynex forks, has undergone an extensive security audit by [OpenZeppelin](https://blog.openzeppelin.com/retro-thena-audit) and [PeckShield](https://github.com/peckshield/publications/tree/master/audit_reports/PeckShield-Audit-Report-Thena-v1.0.pdf).
* **Algebra:** Our DEX infrastructure, developed by Algebra, has been rigorously audited by [ABDK Consulting](https://algebra.finance/static/ABDK_Algebra_Audit-b4a20379efce1d26b7fbe9127582df6a.pdf), [Hexens](https://algebra.finance/static/Hexens_Algebra_Audit-0918594cb7666296d9f57295d9274270.pdf), and [Hacken](https://algebra.finance/static/Hacken_Algebra_Audit-317911476f86c632be77388fa51852c0.pdf), significantly strengthening the security fabric of our platform.

{% hint style="warning" %}
**User Caution Advised:** We remind our users that, while audits reduce risks, they don’t eliminate them completely. Users should review our legal disclaimer thoroughly before using Lynex. For security-related queries or reports, please reach out to us via Discord or our GitHub page.
{% endhint %}


---

# 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://lynex.gitbook.io/lynex-docs/info-and-security/audits.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.