> For the complete documentation index, see [llms.txt](https://docs.inceptionlrt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inceptionlrt.com/resources/audit-reports.md).

# Audit Reports 

To strengthen its security and prioritize the safety of users’s funds, InceptionLRT has undergone external security reports.

Here are all the auditing reports:

* **January 2024 Audit Report by Veridise (Inception v1):**
  * [**Veridise Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/InceptionV1_Veridise.pdf)
* **April 2024 Audit Report by Halborn (Inception v2):**
  * [**Halborn Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/InceptionV2_Halborn.pdf)
* **October 2024 Audit Report (reaudit + Symbiotic Vault)**
  * [**Halborn Report**](https://github.com/inceptionlrt/smart-contracts/blob/feat/halborn_symbiotic_script/audits/Inception_DiamondProxy_SymbioticVault_Halborn.pdf)
* **March 2025 Audit Report (Symbiotic Vault)**
  * [**Oxorio Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/Inception_MellowV2_Symbiotic_Oxorio.pdf)
* **March 2025 Audit Report (Symbiotic Vault)**
  * [**Veridise Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/VAR_inception_250210_smart_contracts_V3.pdf)

## B**ridge:** 

* **April 2024 Audit Report by Halborn:**
  * [**Halborn Report**](https://github.com/inceptionlrt/bridge/blob/master/audits/InceptionBridge_Halborn.pdf)
* **April 2024 Audit Report by Veridise:**
  * [**Veridise Report**](https://github.com/inceptionlrt/bridge/blob/master/audits/InceptionBridge_Veridise.pdf)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inceptionlrt.com/resources/audit-reports.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.