Vidma is pleased to present this audit report outlining our assessment of code, smart contracts, and other important audit insights and suggestions for management, developers, and users.
The audited scope included token, vesting, and staking contracts. The protocol uses ERC2771Forwarder contract to operate on forward requests.
In the vesting contract, the tokens are not locked directly in the contract while the lock function is called so tokens will be locked as per admin when a user buys a subscription. Withdraw of vested tokens is only allowed for the Vester role, and includes some fee based on project performance and gas fee that is reduced from claimed amount. The fee can be transferred to the ecosystem pool by the contract admin.
During the audit process, the Vidma team found several issues, including those with high severity. A detailed summary and the current state are displayed in the table below.
After evaluating the findings in this report and the final state after fixes, the Vidma auditors can state that the contracts are fully operational and secure. Under the given circumstances, we set the following risk level:
To set the codebase quality mark, our auditors are evaluating the initial commit given for the scope of the audit and the last commit with the fixes. This approach helps us adequately and sequentially evaluate the quality of the code. Code style, optimization of the contracts, the number of issues, and risk level of the issues are all taken into consideration. The Vidma team has developed a transparent evaluation codebase quality system presented below.
Evaluating the initial commit and the last commit with the fixes, Vidma audit team set the following codebase quality mark.
Score
Based on the overall result of the audit and the state of the final reviewed commit, the Vidma audit team grants the following score:
In addition to manual check and static analysis, the auditing team has conducted a number of integrated autotests to ensure the given codebase has an adequate performance and security level. The test results and coverage can be found in the accompanying section of this audit report.
Please be aware that this audit does not certify the definitive reliability and security level of the contract. This document describes all vulnerabilities, typos, performance issues, and security issues found by the Vidma audit team.
If the code is still under development, we highly recommend running one more audit once the code is finalized.
Qoodo is a quality management and data tracking application utilizing the innovative technology of the blockchain to help businesses function more efficiently.
Within the scope of this audit, two independent auditors thoroughly investigated the given codebase and analyzed the overall security and performance of the smart contracts.
The audit was conducted from June 23, 2023 to June 26, 2023. The outcome is disclosed in this document.
The scope of work for the given audit consists of the following contracts:
The source code was taken from the following source:
https://github.com/NAPLOZZ/NAP-token-contracts
Initial commit submitted for the audit:
c1030a599b6435406bacf8e6bbd007d3edc59129
Last commit reviewed by the auditing team:
c67d25d5e42d65cf97f50b335bcae01f12a6a3fc
As a reference to the contracts logic, business concept, and the expected behavior of the codebase, the Naplozz team has provided the following documentation:
Vidma audit team uses the most sophisticated and contemporary methods and well-developed techniques to ensure contracts are free of vulnerabilities and security risks. The overall workflow consists of the following phases:
After the Audit kick-off, our security team conducts research on the contract’s logic and expected behavior of the audited contract.
Vidma auditors do a deep dive into your tech documentation with the aim of discovering all the behavior patterns of your codebase and analyzing the potential audit and testing scenarios.
At this point, the Vidma auditors are ready to kick off the process. We set the auditing strategies and methods and are prepared to conduct the first audit part.
During the manual phase of the audit, the Vidma team manually looks through the code in order to find any security issues, typos, or discrepancies with the logic of the contract. The initial commit as stated in the agreement is taken into consideration.
Static analysis tools are used to find any other vulnerabilities in smart contracts that were missed after a manual check.
An interim report with the list of issues.
Within the testing part, Vidma auditors run integration tests using the Truffle or Hardhat testing framework. The test coverage and the test results are inserted in the accompanying section of this audit report.
Second interim report with the list of new issues found during the testing part of the audit process.
For simplicity in reviewing the findings in this report, Vidma auditors classify the findings in accordance with the severity level of the issues. (from most critical to least critical).
All issues are marked as “Resolved” or “Unresolved”, depending on if they have been fixed by project team or not. The issues with “Not Relevant” status are left on the list of findings but are not eligible for the score points deduction.
The latest commit with the fixes reviewed by the auditors is indicated in the “Scope of Work” section of the report.
The Vidma team always provides a detailed description of the issues and recommendations on how to fix them.
Classification of found issues is graded according to 6 levels of severity described below:
High MH – 01 | Resolved
There is the original .env file in the repository last commit. Passwords and private keys are exposed.
Consider adding .env to the .gitignore so the private data won't be exposed by unauthorized users which can lead to the exploit.
Informational MI – 01 | Resolved
Constructor params are changed in the StakingNapTokens, NaplozzToken, EcoSystemPool and YearlyVesting contracts. But the natspec comments are not changed.
Consider updating the natspec comments.
To verify the security of contracts and the performance, a number of integration tests were carried out using the Truffle testing framework.
In this section, we provide both tests written by Naplozz and tests written by Vidma auditors.
Naplozz Coverage – 92%
Vidma Coverage – 100%
Industry Standard – 95%
It is important to note that Vidma auditors do not modify, edit or add tests to the existing tests provided in the Naplozz repository. We write totally separate tests with code coverage of a minimum of 95% to meet the industry standards.
We are delighted to have a chance to work with the Naplozz team and contribute to your company's success by reviewing and certifying the security of your smart contracts.
The statements made in this document should be interpreted neither as investment or legal advice, nor should its authors be held accountable for decisions made based on this document.