# ANZEN Our goal with ANZEN is to ensure that people in DeFi Space have the ability to verify developers. We see that fraud (rug-pulls/scams) have increased rapidly in recent years. Within ANZEN a developer can receive a certificate if he cooperates with the protocol. The protocol consists of 3 different layers of authentication and therefore it is safe. ANZEN will at all times be the intermediary between the buyer and the deployer. As an example, when a deployer registers and cooperates with our protocol, he receives a certificate. When the developer deploys a contract on the relevant network, he can use this certificate and the buyers can verify this certificate within ANZEN. The liquidity can only be unlocked by the developer if he has proven 3 layers of authentication at ANZEN. For example, projects may want to perform a migration and migrate their liquidity. In such a situation, the following aspects are considered: (1) The developer must identify himself, this information will only be shared with the public in the event of fraud. Social media and Community Check, the developer must post on social media at all times that he is going to remove the liquidity for the purpose of migrating it. A certificate is also linked to this. (2) An example of a 2-L (2Layer) security is mentioned above. There is also a possibility for, for example, projects to take an L-3 certificate, but he must also complete the next step: (3) The contract is deployed from the ANZEN Ecosystem, this ensures that scammers cannot add backdoors in the contract. We will provide more information within this whitepaper during the development of the application. Portions of source code will also be made public. --- # 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://taleofsatoshi.gitbook.io/whitepaper/anzen.md?ask= ``` 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.