# Security & Audits

## Overview

Seneca Protocol uses best practices to reduce risk within the protocol and its markets. However, using DeFi applications, including Seneca Protocol, always exposes deposited funds to some level of risk.

### Security Strategy

Seneca Protocol takes the following steps in order to minimize risk:

#### **Third-party Oracles**

Whenever possible, Seneca will prioritize the usage of third-party oracles in order to ensure the transparency and reliability in managing price feeds.

Seneca will primarily employ DIA oracles.

#### **Initial Limits**

Mintable **senUSD** will be limited to a minimum quantity during the protocol's initial phase. This allows for the organic expansion of the **senUSD** supply as well as the discovery of any issues prior to the easing of the stricter borrowing limitations and the opening of the markets to the largest possible user base.

The initial phase of the protocol will have a reduced quantity of borrowable **senUSD**. This enables both the organic growth of the **senUSD** supply and the early detection of any problems, if any, before the stricter limits are lifted and borrowing is fully opened to the broadest audience.

#### **Audits**

To provide the highest level of code safety, Seneca uses trusted, battle-tested codebases for its essential infrastructure components.

To find and fix any potential flaws, top security firms will nevertheless conduct additional examinations of Seneca's smart contracts. Advanced strategies, new asset pricing models, and other unique components will also undergo routine post-launch audits.

#### 🛡️ **CDP Infrastructure Audit**

> **🔗** [**Halborn Security Report**](https://github.com/HalbornSecurity/PublicReports/blob/master/Solidity%20Smart%20Contract%20Audits/Seneca_SenecaDefi_Smart_Contract_Security_Assessment_Report_Halborn_Final.pdf) **(PDF)**


---

# 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://seneca-protocol-docs.gitbook.io/seneca-protocol/overview/security-and-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.