# Paladin Full Audit

![](/files/-MhUhDHTb1SyupOFKKbh)

{% file src="/files/-MlBoLxdd3xqtPDu3Qf9" %}

{% hint style="danger" %}
For a full explaination and instructions on how to verify that we indeed did NOT need to spend $9K on a RugDoc KYC and a second audit for the same code, check out this article: <https://medium.com/@astrofarms/why-we-chose-not-to-spend-9k-on-kyc-and-paladin-audit-for-layer-4-de3134f40514>
{% endhint %}

{% hint style="info" %}
We chose not to pay Paladin thousands of dollars to audit the same code twice.  We've made no changes to our contracts and Masterchef since the audit. Google "code compare" and you will see, all we added was our LIBRA Shield. This gives us the opportunity to give more back to investors. There's a full tutorial with screenshots in the article above.
{% 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://astrofarms.gitbook.io/astrofarms/contracts-security/paladin-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.
