> For the complete documentation index, see [llms.txt](https://polytrade.gitbook.io/polytrade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polytrade.gitbook.io/polytrade/the-basics/verification-manager.md).

# Verification Manager

{% hint style="info" %}
The Polytrade lender pool verification manager will be used to verify the user on the smart contract.
{% endhint %}

Each user has to go under a verification process that may change over time and would have a direct impact on the funds a user can add to the system.

Today we have a KYC/KYB verification system that will allow users to lend higher amounts on the Polytrade system.

### **KYC Limit**

A set amount after which each user must do their KYC. This will be checked each time a user wants to add money to the pool. 

If the total current amount in the pool added by the user is higher than the set **limit**, the user must do KYC. 

At any point, Current deposits Cannot be higher than the KYC limit if the user has not done their KYC.

### **Expected Behavior**

* The **Verification manager** can be changed to a new manager with new **KYC providers**, this should not affect the users who have already been verified.
* Over a period of time**,** a new verification model may be introduced making this redundant this should force a redeployment of the contract.
* The **Verification model** should not have any impact on the reward and strategy manager.
* A function on the smart contract to validate the KYC of a user.
* An option for the Polytrade team is to change the KYC limit, such change will only impact the user's capability to add funds for the future and will have no impact on deposits that have already been made by the user.
* If there are two stable coins available to lend, then the KYC limit will have an effect on the total lent on the Polytrade system. (Outside scope of the contract)

![](/files/noZl2nK9KJ5Y7Wh8sZN9)

### ​​Test case for KYC limit and verification test model

**User current Lends:** 2000$\
**Present KYC Limit:** 5000$

**New Update :**\
**KYC limit:** 0$

**Result: No effect on users' current lending.**

**Users must do KYC before the next funding round.**\
**All new rounds must now have Approved KYC.**

### How **does it** work

![Before Switching Verification](/files/bbBjSKNQRZIX0PClVxcb)

![After Switching Verfication](/files/0s4nlsJGZuZ9nCE0N4v8)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://polytrade.gitbook.io/polytrade/the-basics/verification-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.