Audit name:
[SCA] ROWA | ERC20 + Vesting | Apr2023
Date:
Jul 15, 2023
Table of Content
Introduction
We express our gratitude to the ROWA team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
ROWA is a Web3-based gaming platform that launches competitive games under a single, interconnected ecosystem. Using the platform's utilities, gamers can access high-quality, entertaining games and interact with each other through the in-platform team, guild, and loyalty systems.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20; Vesting |
| Timeline | 27/05/2023 - 18/07/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/rowagames/ROWA-Token→ |
| Commit | 2ecddd50 |
Review Scope
- Repository
- https://github.com/rowagames/ROWA-Token→
- Commit
- 2ecddd50
Audit Summary
10/10
99.04%
10/10
10/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 ROWA |
| Audited By | Hacken |
| Website | https://rowa.games/→ |
| Changelog | 04/05/2023 - Initial Review |
| 15/06/2023 - Second Review | |
| 18/07/2023 - Third Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for ROWA
- Audited By
- Hacken
- Website
- https://rowa.games/→
- Changelog
- 04/05/2023 - Initial Review
- 15/06/2023 - Second Review
- 18/07/2023 - Third Review
System Overview
ROWA Games - is a staking protocol with the following contracts:
RowaToken — ERC-20 ownable, pausable token that mints all initial supply to a deployer. Additional minting is not allowed. Owner can start vesting through a contract. It has the following attributes:
Name: ROWA Token
Symbol: ROWA
Decimals: 5
Total supply: 1b tokens.
RowaVesting — a contract that implements vesting mechanisms for different types of users.
Privileged roles
The owner of the RowaVesting smart contract can start and stop vesting, and release tokens for any user.
The owner of the RowaTokens smart contract can use pausable and snapshot mechanisms. Also it has the possibility to start vesting by transferring all tokens supply to the vesting smart contract.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are partially missing.
Functional requirements related to the tokenomic are provided.
The technical requirements outlining how the system should operate and the necessary components for the smart contract are provided.
Technical description is robust.
Inline comments to describe code behavior have been added.
NatSpec is provided: smart contract description, param description, return values description, validation rules.
Run instructions are provided.
Technical specification is provided.
Code quality
The total Code quality score is 10 out of 10.
Code contains no style issues.
Test coverage
Code coverage of the project is 99.04% (branch coverage), with a mutation score of 49%.
Deployment and basic user interactions are covered with tests.
Negative cases coverage is present.
Interactions with several users are tested.
The tests share similar inaccuracies with the contract logic, resulting in undetected issues.
The comments within these tests do not accurately represent the executed code.
Security score
Upon auditing, the code was found to contain 2 critical, 3 high, 4 medium, and 5 low severity issues. Out of these, 14 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.9. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Risks
Vestings for Team, Advisors, Partnerships can be revoked.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-0248 | Compilation Error | fixed | Critical | |
| F-2023-0247 | Requirements Violation | fixed | Critical | |
| F-2023-0251 | Invalid Calculations; Requirement Violation | fixed | High | |
| F-2023-0250 | Requirement Violation | fixed | High | |
| F-2023-0249 | Requirement Violation | fixed | High | |
| F-2023-0255 | Hash Collision | fixed | Medium | |
| F-2023-0254 | Redundant Safemath Library | fixed | Medium | |
| F-2023-0253 | Invalid Calculations | fixed | Medium | |
| F-2023-0252 | Lock of Native Tokens | fixed | Medium | |
| F-2023-0260 | Constant Variables | 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/rowagames/ROWA-Token→ |
| Commit | 2ecddd50 |
| Whitepaper | Provided→ |
| Requirements | Provided→ |
| Technical Requirements | Provided→ |
Scope Details
- Repository
- https://github.com/rowagames/ROWA-Token→
- Commit
- 2ecddd50
- Whitepaper
- Provided→
- Requirements
- Provided→
- Technical Requirements
- Provided→