Q2 2026 Security & Compliance Report67 incidents, $764M in losses, 88% from operational failures.
Get the report →
GamesCoin (old Magamec) logo

GamesCoin (old Magamec)

Audit name:

[SCA] GamesCoin | BEP20 | Dec2023

Date:

Dec 12, 2023

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 GamesCoin (old Magamec) team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

GamesCoin’s dynamic ecosystem offers a wide range of opportunities, including multi-functional NFT marketplaces for in-game items, cross-game utility of resources and game assets and the creation of the gamer-to-gamer economy.

titlecontent
LanguageSolidity
TagsERC20, BEP20
Timeline23/11/2023 - 14/12/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/Youre-Group/sc-gamescoin→
    Commite3d0597

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    100%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    6Total Findings
    6Resolved
    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 GamesCoin (old Magamec)
    Approved ByGrzegorz Trawinski
    Websitehttp://gamescoin.io/→
    Changelog30/11/2023 - Preliminary Report
    14/12/2023 - Final Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for GamesCoin (old Magamec)
      Approved By
      Grzegorz Trawinski
      Website
      http://gamescoin.io/→
      Changelog
      30/11/2023 - Preliminary Report
      14/12/2023 - Final Report

    System Overview

    GamesCoin is a simple ERC-20 (and BEP-20) compatible fungible token in the GamesCoin.sol contract. The ownership of the contract is transferable.

    It has the following attributes:

    • Name: GamesCoin

    • Symbol: GC

    • Decimals: 5

    • Total supply: 3 billion tokens

    • Minting: 50 million is unlocked for minting every 30 days

    Privileged roles

    The owner of the contract is able to:

    • mint tokens that are unlocked for minting

    • transfer ownership

    • renounce ownership

    Executive Summary

    Documentation quality

    The total Documentation quality score is 10 out of 10.

    • Functional requirements are provided.

    • Technical description is provided in full.

    • NatSpec is provided.

    Code quality

    The total Code quality score is 10 out of 10.

    Test coverage

    Code coverage of the project is 100% (branch coverage).

    Security score

    Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 1 low severity issues. Out of these, 1 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.

    Scoring Methodologyarrow right

    Risks

    The minting start date is hard-coded to be Nov 16, 2023.

    Findings

    F-2023-0744Missing method required in specification
    Status
    fixed
    Severity

    Low
    I-2023-0193Computation is overcomplicated
    Status
    fixed
    Severity

    Observation
    I-2023-0192Immutable variables should be declared as such
    Status
    fixed
    Severity

    Observation
    I-2023-0191Ownership Irrevocability Vulnerability
    Status
    fixed
    Severity

    Observation
    I-2023-0190Custom Errors in Solidity for Gas Efficiency
    Status
    fixed
    Severity

    Observation
    I-2023-0189Floating pragma
    Status
    fixed
    Severity

    Observation
    Code
    ―
    Title
    Status
    Severity
    F-2023-0744Missing method required in specification
    fixed

    Low
    I-2023-0193Computation is overcomplicated
    fixed

    Observation
    I-2023-0192Immutable variables should be declared as such
    fixed

    Observation
    I-2023-0191Ownership Irrevocability Vulnerability
    fixed

    Observation
    I-2023-0190Custom Errors in Solidity for Gas Efficiency
    fixed

    Observation
    I-2023-0189Floating pragma
    fixed

    Observation
    1-6 of 6 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/Youre-Group/sc-gamescoin→
    Commit2586586bc029a84cb8a5d2c27602ef4e1d78e606
    WhitepaperNot provided
    RequirementsProvided
    Technical RequirementsProvided

    Contracts in Scope

    src
    GamesCoin.sol - src › GamesCoin.sol

    Disclaimer