> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/kelp/security/audits.md).

# Audits

Kelp - rsETH has undergone comprehensive audits conducted by highly renowned auditors - SigmaPrime, Code4rena, MixBytes and Bailsec. These audits, carried out by industry-leading experts, have thoroughly evaluated the protocol's security and functionality. The detailed audit reports can be found below.

| Audit Report                                                                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------- |
| [Kelp Smart Contract Audit by Sigma Prime December 2023](https://kelpdao.xyz/audits/smartcontracts/SigmaPrime.pdf)                          |
| [Kelp Smart Contract Audit by Code4rena December 2023](https://code4rena.com/reports/2023-11-kelp)                                          |
| [Kelp Smart Contract Audit by MixBytes March 2024](https://kelpdao.xyz/audits/smartcontracts/mixbytes.pdf)                                  |
| [Kelp Smart Contract Audit by Sigma Prime June 2024](https://kelpdao.xyz/audits/smartcontracts/SigmaPrime_2.pdf)                            |
| [Kelp Smart Contract Audit by Sigma Prime (Withdrawals) June 2024](https://kelpdao.xyz/audits/smartcontracts/SigmaPrime_3.pdf)              |
| [Kelp Smart Contract Audit by Sigma Prime (PEPE Upgrade) September 2024](https://kerneldao.com/kelp/audits/smartcontracts/SigmaPrime_5.pdf) |
| [Kelp Smart Contract Audit by Sigma Prime (rsETH Adaptor) November 2024](https://kerneldao.com/kelp/audits/smartcontracts/SigmaPrime_4.pdf) |
| [Kelp Smart Contract Audit by Sigma Prime June 2025](https://kerneldao.com/kelp/audits/smartcontracts/SigmaPrime_6.pdf)                     |
| [Kelp Smart Contract Audit by Bailsec September 2025](https://kerneldao.com/kelp/audits/smartcontracts/Bailsec_rsETH_november.pdf)          |
| [Kelp Smart Contract Audit by Bailsec December 2025](https://kerneldao.com/kelp/audits/smartcontracts/Bailsec_rsETH_december_2025.pdf)      |
| [Kelp Smart Contract Audit by Bailsec May 2026](https://kerneldao.com/kelp/audits/smartcontracts/Bailsec_rsETH_May_2026.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://kerneldao.gitbook.io/kernel/getting-started/kelp/security/audits.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.