# Security

The security of the protocol is our highest priority, dForce development team works closely with third-party auditors and formal verification teams to ensure that the protocols match the highest security standards.

### Audits

{% hint style="success" %}
[**ConsenSys Deligence *****Audit***** - April 2021**](https://consensys.net/diligence/audits/2021/03/dforce-lending-protocol-review/)
{% endhint %}

{% hint style="success" %}
[**Trail of Bits *****Audit***** - March 2021**](https://github.com/dforce-network/documents/blob/master/audit_report/Lending/dForceLending-Audit-Report-TrailofBits-Mar-2021.pdf)
{% endhint %}

{% hint style="success" %}
[**Certora *****Formal Verification***** - March 2021**](https://www.certora.com/pubs/dForceFeb2021.pdf)
{% endhint %}

{% hint style="success" %}
[**Certik *****Audit***** - February 2021**](https://www.certik.org/projects/dforce)
{% endhint %}

### Bug Bounty

We encourage the hunting of bugs and potential exploits in our protocols, Refer to our [bug bounty program](https://docs.dforce.network/devs/bug-bounty) for details.


---

# 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://developers.dforce.network/lend/lend-and-synth/security.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.