# 🔐Security

## **Rug-proof ✅**&#x20;

Our liquidity has been burned in order to ensure security and to give strength to the $DUFF token.(<https://polygonscan.com/tx/0xd6b73bba0108cddcaa725a7c564251477a72f5ea82f9389a57fa2bc2d5c14ad8>)

Polysa was designed to ensure security for investors, take a look at our contracts on [**Github**](https://github.com/Polysafi)

## **Harvest lockup** :key:&#x20;

Harvest lockup provides the necessary protection against bots, as well as investors wishing to play with the price of the token. This protection is therefore an essential pillar of the project.

## **Anti-whale protection 🐋**

We need to be careful about the control and manipulation of the market by large holders commonly referred to as "whales". Generally, these large token holders can have too much control over the platform and can have a large impact on market movements. This is why an anti-whale system has been put in place, to support small investors in the market.

## Audit 📃 <a href="#audit" id="audit"></a>

Audits with several verified third-party auditors are on their ways, feel free to check the roadmap!


---

# 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://polysafinance.gitbook.io/polysa-finance/security/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.
