Audit name:
[SCA] InQubeta | ERC20 | May2023
Date:
May 18, 2023
Table of Content
Introduction
We express our gratitude to the InQubeta team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
InQubeta is an NFT crypto crowdfunding platform for AI Tech.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 10/05/2023 - 19/05/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/techbandorg/InQubeta-smartcontract→ |
| Commit | 6bbaa3cead90678115377eadcf7188d1e823f223 |
Review Scope
- Commit
- 6bbaa3cead90678115377eadcf7188d1e823f223
Audit Summary
10/10
100%
9/10
9/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 InQubeta |
| Audited By | Hacken |
| Website | https://inqubeta.ai/→ |
| Changelog | 17/05/2023 - Initial Review |
| 19/05/2023 - Second Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for InQubeta
- Audited By
- Hacken
- Website
- https://inqubeta.ai/→
- Changelog
- 17/05/2023 - Initial Review
- 19/05/2023 - Second Review
System Overview
The scope of this audit is an ERC20 token contract with a fixed supply and burn functionality, that has additional functionality to take fees from UniSwapV2 pairs. The fee amounts and pair addresses are controlled by the fee distributor role, which can be set and changed by the owner of the contract.
The files in the scope:
IFeeCollector.sol: The interface for recording buy and sell fees that took place.
InQubeta.sol: The ERC20 token with fixed supply, burnability, and fee functionality for transfers involving UniswapV2 pairs.
Privileged roles
Default Admin: Set FEEDISTRIBUTORROLE, set fees, add/remove pairs.
FEE_DISTRIBUTION_ROLE: Disable/enable fees, collect fees.
Executive Summary
Documentation quality
The total Documentation quality score is 9 out of 10.
Functional requirements are detailed.
Technical description is provided, but fee logic is not explained with precision.
Description of the development environment is present.
NatSpec is present.
Code quality
The total Code quality score is 9 out of 10.
The development environment is configured.
Solidity style guides are not followed.
Test coverage
Code coverage of the project is 100% (branch coverage).
Since the audit scope has lines of code less than 250, the test coverage does not contribute to the final score.
Security score
Upon auditing, the code was found to contain 1 critical, 0 high, 0 medium, and 1 low severity issues. Out of these, 2 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
The comprehensive audit of the customer's smart contract yields an overall score of 9.7. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Risks
The fee amounts can be changed by the Default Admin Role at any moment.
The fee-on-transfer mechanism will significantly increase the Gas cost of the DEX swaps for pairs added to the fee mechanism.
The implementation of IFeeCollector.sol is out of this audits scope and the safety of its usage in InQubeta.sol contract cannot be verified.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-0701 | Access Control Violation | fixed | Critical | |
| F-2023-0702 | Copying of Well-Known Contract | fixed | Low | |
| I-2023-0166 | Style Guide Violation / Function Order | unfixed | Observation |
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/techbandorg/InQubeta-smartcontract→ |
| Commit | 6bbaa3cead90678115377eadcf7188d1e823f223 |
| Whitepaper | Not provided |
| Requirements | Provided→ |
| Technical Requirements | Provided→ |