Q2 2026 Security & Compliance Report67 incidents, $764M in losses, 88% from operational failures.
Get the report →
Gaimin.io logo

Gaimin.io

Audit name:

[SCA] Gaimin | Wallet | Mar2024

Date:

Apr 12, 2024

Table of Content

→Introduction
→Audit Summary
→Document Information
→System Overview
→Executive Summary
→Risks
→Findings
→Appendix 1. Severity Definitions
→Appendix 2. Scope
→Disclaimer

Want a comprehensive audit report like this?

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's token, GMRX, is a utility token that is used within the GAIMIN ecosystem. It is used to incentivize gamers to contribute their computational resources to gaimin. cloud and is also used for purchasing in-game items and participating in the Gaimin Gladiators eSports platform.

titlecontent
PlatformEVM
LanguageSolidity
TagsVesting
Timeline25/03/2024 - 28/03/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/Gaimin-io-Limited/gmrx-vesting/→
    Commit81573c08cf43e83d85d66fb1fd6593aef38703b3
    Deployed contracthttps://bscscan.com/address/0x6212ea5f43481A91F3352aB091C11E48B06F4126→

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    N/A %

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    1Total Findings
    0Resolved
    0Accepted
    0Mitigated

    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

    NameSmart Contract Code Review and Security Analysis Report for Gaimin.io
    Audited ByMaksym Fedorenko, Roman Tiutiun
    Approved ByGrzegorz Trawinski
    Websitehttps://www.gaimin.io/→
    Changelog28/03/2024 - Preliminary Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Gaimin.io
      Audited By
      Maksym Fedorenko, Roman Tiutiun
      Approved By
      Grzegorz Trawinski
      Website
      https://www.gaimin.io/→
      Changelog
      28/03/2024 - Preliminary Report

    System Overview

    GAIMIN's token, GMRX, is a utility token that is used within the GAIMIN ecosystem. It is used to incentivize gamers to contribute their computational resources to gaimin. cloud and is also used for purchasing in-game items and participating in the Gaimin Gladiators eSports platform. with the following contracts:

    • TimeLockedWallet Contract  —  is a smart contract written in Solidity for the BNB blockchain. It is designed to lock a certain amount of ERC20 tokens for a specified period of time. The contract uses the OpenZeppelin library for secure and standardized contract development.

    • TimeLockedWalletFactory Contract — a contract serves as a factory for deploying new instances of the TimeLockedWallet contract.

    Privileged roles

    • The owner of the TimeLockedWalletFactory contract can set the token address, and set TLW address.

    • The owner of the TimeLockedWallet contract can validate initialize.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 10 out of 10.

    • Functional requirements are provided.

    • Technical description is provided.

    Code quality

    The total Code Quality score is 10 out of 10.

    Test coverage

    Code coverage of the project is under 250 Lines of Code is not considered within the security score.

    Security score

    Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 0 low severity 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 10. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Scoring Methodologyarrow right

    Risks

    No risks were identified.

    Findings

    F-2024-1781Initializer Is Not Disabled In Constructor
    Status
    unfixed
    Severity

    Observation
    Code
    ―
    Title
    Status
    Severity
    F-2024-1781Initializer Is Not Disabled In Constructor
    unfixed

    Observation
    1-1 of 1 findings

    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

    Repositoryhttps://github.com/Gaimin-io-Limited/gmrx-vesting/→
    Commit81573c08cf43e83d85d66fb1fd6593aef38703b3
    Deployed contracthttps://bscscan.com/address/0x6212ea5f43481A91F3352aB091C11E48B06F4126→
    Whitepaperhttps://github.com/Gaimin-io-Limited/gmrx-vesting/blob/main/README.md→
    Requirementshttps://github.com/Gaimin-io-Limited/gmrx-vesting/blob/main/README.md→
    Technical Requirementshttps://github.com/Gaimin-io-Limited/gmrx-vesting/blob/main/README.md→

    Contracts in Scope

    contracts
    TimeLockedWallet.sol - contracts › TimeLockedWallet.sol
    TimeLockedWalletFactory.sol - contracts › TimeLockedWalletFactory.sol

    Disclaimer