> For the complete documentation index, see [llms.txt](https://lend-finance-organization.gitbook.io/lendx-documentation-v1.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lend-finance-organization.gitbook.io/lendx-documentation-v1.0/legitimacy/audit-report.md). # Audit Report {% embed url="" %} **Audit Scope** This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested. We will verify the following claims: * Correct implementation of Token standard * Deployer cannot mint any new tokens * Deployer cannot burn or lock user funds * Deployer cannot pause the contract * Overall checkup (Smart Contract Security) The auditing process follows a routine series of steps: * Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract. * Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities. * Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe. * Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases. * Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute. * Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research. * Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts. *A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.*