> For the complete documentation index, see [llms.txt](https://docs.solera.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solera.market/protocol/audits.md).

# Audits

<sup>*While audit reports are essential to the security of any DeFi application, internal and external assessments do not provide any warranties; evaluation results from past and future audit reports do not guarantee the absence of any subsequent issues with the smart contracts and platforms they are deployed onto.*</sup>&#x20;

### **December 18th 2024: Lending Core Audit**

By Zenith / Code4rena

{% file src="/files/QaZnwj5hGFns1CdShAJl" %}

### **February 4th 2025: Liquid Staking Core Audit**

By Zellic

{% file src="/files/7C3rVcPXTdKffsuwjAXf" %}

### **March 19th 2025: Leveraged Strategy Modules Audit**

By Zellic

{% file src="/files/sszGccPbREZxxPCCszx2" %}

### **May 27th 2025: Comprehensive review**

By Octane Security


---

# 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://docs.solera.market/protocol/audits.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.