Audit name:
[SCA] Gaimin.io / Vesting / Dec2023
Date:
Jan 10, 2024
Table of Content
Introduction
We express our gratitude to the Gaimin.io team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Gaimin is a token that will be used during the vesting process.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | BEP-20 |
| Timeline | 26/12/23 - 03/01/24 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Last Review Scope | |
|---|---|
| Repository | https://github.com/Gaimin-io-Limited/gmrx-vesting/tree/main→ |
| Commit | 6429225 |
Last Review Scope
- Commit
- 6429225
Audit Summary
10/10
0%
10/10
8/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 Gaimin.io |
| Audited By | Viktor Lavrenenko |
| Approved By | Przemyslaw Swiatowiec, Ataberk Yavuzer |
| Website | http://gaimin.io/→ |
| Changelog | 03/01/2024 - Final Report |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Gaimin.io
- Audited By
- Viktor Lavrenenko
- Approved By
- Przemyslaw Swiatowiec, Ataberk Yavuzer
- Website
- http://gaimin.io/→
- Changelog
- 03/01/2024 - Final Report
System Overview
Gaimin Token is a vesting token with the following contracts:
GMRX — simple BEP-20 token that mints all initial supply to a deployer. Additional minting is not allowed.
It has the following attributes:
Name: Gaimin Token.
Symbol: GMRX.
Decimals: 18.
Total supply: 100 billion tokens.
Privileged roles
The contract does not have any roles.
Executive Summary
Documentation quality
The total Documentation Quality score is 8 out of 10.
Functional requirements are partially provided:
Business logic is partially provided: the total supply of GMRX, which is 100.000.000.000 is not documented.
The technical description is partially provided:
NatSpec is sufficient, since it is inherited from OpenZeppelin.
A description of the development environment is missing.
Technical specification is provided.
Code quality
The total Code Quality score is 10 out of 10.
All best practices are followed.
The development environment is configured.
Test coverage
Code coverage of the project is 0% (branch coverage).
For projects with less than 250 LOC (Lines of Code) the test coverage is not mandatory, and it is not accounted for in the final score.
Security score
Upon auditing, the code was found to contain 0 issues, 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.8. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Risks
All tokens are minted to a single address. The secureness of the supply depends on the secureness of key storage.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-0310 | Floating Pragma | fixed | Observation |
Identify vulnerabilities in your smart contracts.
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/Gaimin-io-Limited/gmrx-vesting/tree/main→ |
| Commit | 6429225 |
| Whitepaper | Whitepaper→ |
| Requirements | Whitepaper→ |
| Technical Requirements | NatSpec→ |
Scope Details
- Commit
- 6429225
- Whitepaper
- Whitepaper→
- Requirements
- Whitepaper→
- Technical Requirements
- NatSpec→
Deployed contract [code] →
Contracts in Scope
contracts/GMRX.sol