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

# Audits

AbraFi Labs understands the vital importance of smart contract security and testing rigor. We seek to maintain a comprehensive audit process to mitigate the risk of vulnerabilities,  logic errors, or inefficiencies. We provide visibility to all 3rd party audit reports with transparent remediation processes.&#x20;

### Audit Reports

#### Zokyo initial contract audit

This report surfaced one critical vulnerability where first staker can drain prefunded vault value in sUSDAF. The issue was resolved and the audit was completed with a perfect score of 100 after remediation.&#x20;

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

#### Certora & Solana Foundation due diligence audit

This audit was performed on protocol contracts to assess the forward-looking audit requirements. It acknowledges additional audits are recommended to review vesting, rewards and staking as they become available in the codebase.&#x20;

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


---

# 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://abrafi.gitbook.io/abrafi-docs/resources/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.
