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

Galaxis

Audit name:

[SCA] Galaxis | Contract | May2024

Date:

May 22, 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 Galaxis team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

Galaxis is a web3-based, distributed membership card-based community management system with a built-in economy. Galaxis Token serves as the native utility token and empowers economic transactions, membership privileges, utility integration, grants distribution, staking rewards, and governance participation within the Galaxis ecosystem.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC-20
Timeline08/05/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/ethercards/GALAXIS-Token→
    Commit2ee4a77a4141f365b6562455e354dc756d580fdc

    Audit Summary

    Total9.3/10
    Security Score

    10/10

    Test Coverage

    100%

    Code Quality Score

    7/10

    Documentation Quality Score

    9/10

    4Total 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 Galaxis
    Audited ByAlkautsar Fatahillah
    Approved ByTurgay Arda Usman
    WebsiteN/A
    Changelog08/05/2024 - Preliminary Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Galaxis
      Audited By
      Alkautsar Fatahillah
      Approved By
      Turgay Arda Usman
      Website
      N/A
      Changelog
      08/05/2024 - Preliminary Report

    System Overview

    Galaxis is an ERC-20 with the following contracts:

    Galaxis Token  — simple ERC-20 token that mints all initial supply to SAFE address. Additional minting is restricted only to SAFE address.

    It has the following attributes:

    • Name: GALAXIS Token

    • Symbol: GALAXIS

    • Decimals: 18

    • Initial supply: 7.5b tokens

    • Total supply: 10b tokens.

    Privileged roles

    • The SAFE address is able to mint additional tokens as long as the additional supply + initial supply does not exceed the maximum supply.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 9 out of 10.

    • Functional requirements are provided.

    • Technical requirements are provided.

    • Natspec is missing.

    Code quality

    The total Code quality score is 7 out of 10.

    • The development environment is configured.

    • There is a redundant check found in the code.

    • Some state variables do not adhere to Solidity best practices.

    Test coverage

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

    • Tests are not mandatory for code less than 250 lines of codes.

    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 9.3. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Scoring Methodologyarrow right

    Risks

    All the tokens are minted to a single address. The secureness of the supply relies solely on the security of key storage mechanisms.

    Findings

    F-2024-2359Redundant check for initialSupply in constructor
    Status
    unfixed
    Severity

    Observation
    F-2024-2351State variables only set in their definitions should be declared constant
    Status
    unfixed
    Severity

    Observation
    F-2024-2350Large multiples of ten should use scientific notation (e.g. 1e6) rather than decimal literals (e.g. 1000000), for readability
    Status
    unfixed
    Severity

    Observation
    F-2024-2349Missing zero address validation when updating safe address in constructor
    Status
    unfixed
    Severity

    Observation
    Code
    ―
    Title
    Status
    Severity
    F-2024-2359Redundant check for initialSupply in constructor
    unfixed

    Observation
    F-2024-2351State variables only set in their definitions should be declared constant
    unfixed

    Observation
    F-2024-2350Large multiples of ten should use scientific notation (e.g. 1e6) rather than decimal literals (e.g. 1000000), for readability
    unfixed

    Observation
    F-2024-2349Missing zero address validation when updating safe address in constructor
    unfixed

    Observation
    1-4 of 4 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:

    Contracts in Scope

    contracts
    GALAXIS.sol - contracts › GALAXIS.sol

    Disclaimer