# Security Audits

At Prodigy.Fi, smart contract security is a core priority. Our contracts undergo independent security reviews and iterative testing to surface edge cases, implementation risks, and economic attack vectors before deployment. This helps the protocol run reliably and gives users confidence through clear and transparent practices.

### 1. Halborn v1 Audits - October 2024

We conducted our initial audit with [Halborn](https://www.halborn.com/audits/prodigy/prodigy---smart-contract-audit-bf0d77) on the v1 contracts of our structured yield vaults on Prodigy.Fi, where issues found were all addressed and resolved.

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

### 2. Security Advisory with Pashov - July 2025 Onwards

Additionally, we worked closely with a dedicated auditor from [Pashov](https://x.com/PashovAuditGrp/status/1940758172261830816) on an advisory basis, giving us continuous security guidance throughout development beyond formal audit cycles.

### 3. Sherlock v1 Audits - October 2025

After upgrading our contracts and shipping multiple new updates, we conducted a second audit with [Sherlock](https://github.com/sherlock-protocol/sherlock-reports/blob/main/audits/2025.12.09%20-%20Final%20-%20Prodigy%20Finance%20Collaborative%20Audit%20Report%201765292688.pdf). The findings of the report shows no critical issues found, and all minor issues were rectified.

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


---

# 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://prodigyfi.gitbook.io/structured-yields/welcome/security-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.
