Audit name:
[SCA] Reneverse | ERC20 | May2023
Date:
Jun 10, 2023
Table of Content
Introduction
We express our gratitude to the ReneVerse team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
ReneVerse is an end-to-end solution that brings gaming asset interoperability to any Web2/Web3 game.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 26/05/2023 - 12/06/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/ReneVerse/rene-defi→ |
| Commit | 4488baaf93bce439d10877e8d1fbd2edcc5487e1 |
Review Scope
- Repository
- https://github.com/ReneVerse/rene-defi→
- Commit
- 4488baaf93bce439d10877e8d1fbd2edcc5487e1
Audit Summary
10/10
0%
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 ReneVerse |
| Audited By | Hacken |
| Website | https://reneverse.io→ |
| Changelog | 01/06/2023 - Initial Review |
| 12/06/2023 - Second Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for ReneVerse
- Audited By
- Hacken
- Website
- https://reneverse.io→
- Changelog
- 01/06/2023 - Initial Review
- 12/06/2023 - Second Review
System Overview
Reneverse is a gaming protocol with the following ERC20 token contract:
RENE — a simple ERC-20 token contract, which mints part of the supply to a system address. It has the following attributes:
Name: Rene Token
Symbol: RENE
Decimals: 18
Total supply: 500m tokens.
Privileged roles
No privileged roles.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are present but only in a limited capacity:
Tokenomic description is provided.
Basic system description is provided.
Technical description is provided:
Run instructions are provided.
NatSpec is sufficient.
Technical specification is provided.
Code quality
The total Code quality score is 10 out of 10.
Code contains no quality violations.
Test coverage
Code coverage of the project is 0%.
Tests are not provided.
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 0 low severity issues. Out of these, 0 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 10. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| I-2023-0069 | Unused Import | fixed | Observation | |
| I-2023-0068 | Floating Pragma | fixed | 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/ReneVerse/rene-defi→ |
| Commit | 4488baaf93bce439d10877e8d1fbd2edcc5487e1 |
| Whitepaper | Not provided |
| Requirements | Provided→ |
| Technical Requirements | Provided→ |
Scope Details
- Repository
- https://github.com/ReneVerse/rene-defi→
- Commit
- 4488baaf93bce439d10877e8d1fbd2edcc5487e1
- Whitepaper
- Not provided
- Requirements
- Provided→
- Technical Requirements
- Provided→