The Hacken 2025 Yearly Security ReportCovers major Web3 breaches, their root causes, prevention insights, and key regulatory trends for 2026.
Learn more

OGz club

Audit name:

[SCA] OGX | ERC20 | Jun2023

Date:

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

OGz is the pioneering MemeFi project that strives to create a thriving community by incorporating the beloved Meme culture with DeFi.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20
Timeline15/05/2023 - 09/06/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/mastiodotco/ogz-smart-contract→
    Commit44491006ff58ff4d26d25d15b777524fee784ace

    Audit Summary

    Total5.9/10
    Security Score

    10/10

    Test Coverage

    26.39%

    Code Quality Score

    8/10

    Documentation Quality Score

    7/10

    31Total Findings
    24Resolved
    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 OGZ
    Audited ByHacken
    Changelog15/05/2023 – Initial Review
    30/05/2023 - Second Review
    09/06/2023 - Third Review

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for OGZ
      Audited By
      Hacken
      Changelog
      15/05/2023 – Initial Review
      30/05/2023 - Second Review
      09/06/2023 - Third Review

    System Overview

    OGZ is an ERC20 token with an affiliate program and fees.

    Privileged roles

    Owner:

    • Can initialize referral data for the new token contract.

    • Can add a list of preferred accounts for nickname creation.

    • Can remove a list of preferred accounts for nickname creation.

    • Can disable the preferred nickname creation feature.

    • Can enable trading.

    Tax manager:

    • Can renounce the Tax Manager Role.

    • Can transfer the Tax manager Role.

    • Can add a list of addresses to the tax-free list.

    • Can remove a list of addresses to the tax-free list.

    • Can change the address of a specific pool.

    • Can disable the buy tax fee for a specific pool.

    • Can disable the sell tax fee for a specific pool.

    • Can disable the reference fee.

    • Can decrease the buy tax fee of a specific pool.

    • Can decrease the sell tax fee of a specific pool.

    • Can decrease the reference fee.

    Preferred Account:

    • Can create a nickname.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 7 out of 10.

    • Functional requirements are partially missing.

    • Technical description is provided.

    • NatSpecs are missing for few functions.

    Code quality

    The total Code quality score is 8 out of 10.

    • Solidity Style Guide is not followed perfectly.

    • There are a few code quality issues.

    • There are a few optimization issues.

    • The development environment is configured.

    Test coverage

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

    • Most of the functions are not covered with tests.

    • The test suite is not configured to run without adding API keys.

    Security score

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

    Scoring Methodologyarrow right

    Risks

    Fees for trading operations are charged from users. Though, those fees are only applicable for swaps that are made in one single pool.

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2023-0999 Requirement Violation - Contradiction
    fixed

    High
    F-2023-0998Data Consistency
    fixed

    High
    F-2023-0997Implementation Error
    fixed

    High
    F-2023-0996 Requirement Violation
    fixed

    High
    F-2023-1004Requirement Violation
    fixed

    Medium
    F-2023-1003 Implementation Error
    fixed

    Medium
    F-2023-1002Authorization through tx.origin
    fixed

    Medium
    F-2023-1001Data Consistency
    fixed

    Medium
    F-2023-1000Denial of Service Vulnerability
    fixed

    Medium
    F-2022-1013Inefficient Gas Model
    unfixed

    Low
    1-10 of 31 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/mastiodotco/ogz-smart-contract→
    Commit44491006ff58ff4d26d25d15b777524fee784ace
    WhitepaperProvided
    RequirementsNot provided
    Technical RequirementsProvided

    Contracts in Scope

    OGzClub.sol - OGzClub.sol

    Disclaimer

    OGz club audit by Hacken