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

Audit name:

[SCA] Race Kingdom LTD | Staking | Jun2022

Date:

Jun 24, 2022

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 Race Kingdom Limited team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

Race Kingdom Limited is an animal racing metaverse that offers several key contracts to facilitate its ecosystem. The RaceKingdom contract issues a BEP-20 token named ATOZ, with a fixed initial supply minted to a deployer and no provision for additional minting.

titlecontent
PlatformEVM
LanguageSolidity
TagsVesting; ERC20
Timeline16/06/2022 - 24/06/2022
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/racekingdom/smart-contract→
    Commit93057ad60b2938b3f7cdac00bdff7cf907902a16

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    10/10

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    7Total Findings
    7Resolved
    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 Race Kingdom Limited
    Audited ByHacken
    Websitehttps://racekingdom.io→
    Changelog16/06/2022 - Initial Review
    24/06/2022 - Second Review
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Race Kingdom Limited
      Audited By
      Hacken
      Changelog
      16/06/2022 - Initial Review
      24/06/2022 - Second Review

    System Overview

    Race Kingdom is an animal racing metaverse with the following contracts:

    RaceKingdom  — simple ERC20 token that mints all initial supply to addresses that will be used in vestings. Additional minting is not allowed. The token has the following attributes:

    • Name: Race Kingdom

    • Symbol: ATOZ

    • Decimals: 18

    • Total supply: 3.7b tokens.

    RKVesting - a contract that is responsible for the control of vesting periods and unlocks.

    Privileged roles

    • The owner of the RKVesting contract can revoke the vesting schedule for a specific identifier.

    • The owner of the RKVesting contract can withdraw exceeded tokens from the vesting pool.

    • The owner of the RKVesting contract can create a vesting schedule for a beneficiary.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 10 out of 10.

    • The Customer provided documentation that adequately described vesting logic.

    Code quality

    The total Code quality score is 10 out of 10.

    • Code is well-formatted, easy-readable, and without duplications.

    • Good unit test coverage.

    Architecture quality

    The Architecture quality score is 10 out of 10.

    • Logic is separated in different files, following the single responsibility principle.

    Security score

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

    Risks

    In case of an admin keys leak, an attacker can lock all token transactions or change vestings.

    Findings

    F-2022-1595Vesting requirements compliance
    Status
    fixed
    Severity

    High
    F-2022-1596Stuck funds in the contract
    Status
    fixed
    Severity

    Medium
    F-2022-1601Variable Shadowing
    Status
    fixed
    Severity

    Low
    F-2022-1600Missing vesting validation
    Status
    fixed
    Severity

    Low
    F-2022-1599Redundant payable address cast
    Status
    fixed
    Severity

    Low
    F-2022-1598Zero address is allowed
    Status
    fixed
    Severity

    Low
    F-2022-1597The public function could be declared external
    Status
    fixed
    Severity

    Low
    Code
    ―
    Title
    Status
    Severity
    F-2022-1595Vesting requirements compliance
    fixed

    High
    F-2022-1596Stuck funds in the contract
    fixed

    Medium
    F-2022-1601Variable Shadowing
    fixed

    Low
    F-2022-1600Missing vesting validation
    fixed

    Low
    F-2022-1599Redundant payable address cast
    fixed

    Low
    F-2022-1598Zero address is allowed
    fixed

    Low
    F-2022-1597The public function could be declared external
    fixed

    Low
    1-7 of 7 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/racekingdom/smart-contract→
    Commit93057ad60b2938b3f7cdac00bdff7cf907902a16
    WhitepaperNot provided
    Technical RequirementsProvided

    Contracts in Scope

    contracts
    RaceKingdom.sol - contracts › RaceKingdom.sol
    RKVesting.sol - contracts › RKVesting.sol

    Disclaimer