Introduction
UACatsDivision is an NFT collection of 10,000 unique cats on the Ethereum blockchain. Each cat is unique and generated with more than 100 different options of emotions, clothes, etc.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Timeline | 16/02/2023 - 20/02/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/uacatsdivision-dev/uacatsdivision-contract→ |
| Commit | 8471531e96a5fed4a3a02ae813deec7d5dd1b1cf |
Review Scope
- Commit
- 8471531e96a5fed4a3a02ae813deec7d5dd1b1cf
Audit Summary
10/10
63.33%
10/10
5/10
The system users should acknowledge all the risks summed up in the risks section of the report
Document Information
This report may contain confidential information about IT systems and the intellectual property of the Customer, as well as information about potential vulnerabilities and methods of their exploitation.
The report can be disclosed publicly after prior consent by another Party. Any subsequent publication of this report shall be without mandatory consent.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for UACatsDivision |
| Audited By | Hacken |
| Website | https://uacatsdivision.com/→ |
| Changelog | 16/06/2023 - Initial Review |
| 20/02/2023 - Second Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for UACatsDivision
- Audited By
- Hacken
- Website
- https://uacatsdivision.com/→
- Changelog
- 16/06/2023 - Initial Review
- 20/02/2023 - Second Review
System Overview
UACatsDivision is an NFT collection of 10,000 unique cats on the Ethereum blockchain. Each cat is unique and generated with more than 100 different options of emotions, clothes, etc.
Quantity – 10,000 NFT
Blockchain – Ethereum
Cost – 0,065 ETH
Standard – ERC-721
Royalty – 5% (All funds will be sent to charity and aid for Ukraine)
Privileged roles
The contract has one privileged role: owner, with the following permissions:
Stop and resume the sale at any time.
Mint arbitrary amount of tokens for free. No tokens can be minted if the total supply is reached.
Withdraw native coins collected on the contract.
Set up baseURI and _contractURI.
Executive Summary
Documentation quality
The total Documentation Quality score is 5 out of 10.
Functional requirements are provided in the Readme file. Basic requirements are provided.
Technical description is not provided.
Code quality
The total Code quality score is 10 out of 10.
Code follows Solidity style guidelines.
Development environment is configured.
Test coverage
Code coverage of the project is 63.33% (branch coverage).
Part of the functionality is not covered.
Multiple-user interactions are not covered.
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 2 medium, and 3 low severity issues. Out of these, 3 issues have been addressed and resolved, leading to a security score of 10 out of 10.
All identified issues are detailed in the “Findings” section of this report.
Summary
According to the assessment, the Customer's smart contract has the following score: 9.5.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-O133 | Redundant values | mitigated | Medium | |
| F-2023-O133 | Inconsistent data | mitigated | Medium | |
| F-2023-O134 | Floating Pragma | fixed | Low | |
| F-2023-1341 | Best practices violation | fixed | Low | |
| F-2023-1340 | Missing 0 value validation | fixed | Low |
Appendix 1. Severity Definitions
When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.
Reference on how risk scoring is done is available through the repository in our Github organization:
Severity | Description |
|---|---|
Critical | Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation. |
High | High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation. |
Medium | Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category. |
Low | Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution, do not affect security score but can affect code quality score. |
Severity
- Critical
Description
- Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.
Severity
- High
Description
- High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.
Severity
- Medium
Description
- Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.
Severity
- Low
Description
- Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution, do not affect security score but can affect code quality score.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | https://github.com/uacatsdivision-dev/uacatsdivision-contract→ |
| Commit | 8471531e96a5fed4a3a02ae813deec7d5dd1b1cf |
| Whitepaper | Not provided |
| Requirements | Provided |
| Technical Requirements | Not provided |
Scope Details
- Commit
- 8471531e96a5fed4a3a02ae813deec7d5dd1b1cf
- Whitepaper
- Not provided
- Requirements
- Provided
- Technical Requirements
- Not provided