2024 Web3 Security ReportAccess control exploits account for nearly 80% of crypto hacks in 2024.
Discover report insights
  • Hacken
  • Audits
  • cryptopia
  • [SCA] Cryptopia / Token-contracts / Feb2024
Cryptopia logo

Cryptopia

Audit name:

[SCA] Cryptopia / Token-contracts / Feb2024

Date:

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

Cryptos Token, the token within a blockchain game in development, serves the purpose of facilitating seamless interoperability across multiple blockchains.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20, Gaming
Timeline15/02/2024 - 16/02/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/cryptopia-com/cryptopia-token-contracts→
    Commit43b3561

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    100%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    9Total Findings
    8Resolved
    1Accepted
    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 Cryptopia
    Audited ByPhilipp Eder
    Approved ByYves Toiser
    Websitehttps://hacken.io→
    Changelog20/02/2024 - Preliminary Report & 22/02/2024 - Final Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Cryptopia
      Audited By
      Philipp Eder
      Approved By
      Yves Toiser
      Website
      https://hacken.io→
      Changelog
      20/02/2024 - Preliminary Report & 22/02/2024 - Final Report

    System Overview

    Cryptopia is an upcoming blockchain game.

    CryptosToken — simple ERC-20 token that mints all initial supply to a deployer. It is intended to have implementations on both Ethereum Mainnet and Polygon Mainnet and comes with functionality to allow seamless bridging.

    It has the following attributes:

    • Name: Cryptos

    • Symbol: TOS

    • Decimals: 18

    • Total supply: 10 billion tokens.

    CryptosTokenPolygon - the implementation of CryptosToken on the Polygon blockchain.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 10 out of 10.

    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 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.

    Risks

    The security of the bridging functionality is dependent on the security of the polygon bridge which was not subject of examination within the scope of this audit.

    The owners need to be trusted to utilize the official polygon bridge as the depositor in CryptosTokenPolygon.sol

    The owners need to be trusted to facilitate the mapping of the rootChain contract and childChain contract correctly in order for the bridging process to work as intended.

    The version of Solidity used in this project might not work on all chains, due to the opcode push0, however it is supported by the chains it is intended to be used on.

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2024-0932Redundant contract structure - AccessErrors.sol
    accepted

    Observation
    F-2024-0931Redundant contract structure - CryptopiaERC20Retriever.sol
    fixed

    Observation
    F-2024-0930Functions not called internally can be marked as external
    fixed

    Observation
    F-2024-0929Missing zero address checks
    fixed

    Observation
    F-2024-0928Variables only set in constructor() should be marked as immutable
    fixed

    Observation
    F-2024-0923Variable shadowing in CryptopiaERC20.sol
    fixed

    Observation
    F-2024-0922Missing event emission
    fixed

    Observation
    F-2024-0865CryptosTokens will be locked inside the contract if sent by accident
    fixed

    Observation
    F-2024-0863Floating pragma
    fixed

    Observation
    1-9 of 9 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/cryptopia-com/cryptopia-token-contracts→
    Commit43b35619a25616c6873d384891a499c13f8af03f
    Whitepaper
    Requirements
    Technical Requirements

    Contracts in Scope

    contracts
    source
    CryptopiaERC20.sol - contracts/source/CryptopiaERC20.sol
    errors
    AccessErrors.sol - contracts/source/errors/AccessErrors.sol
    ArgumentErrors.sol - contracts/source/errors/ArgumentErrors.sol
    ethereum
    CryptosToken.sol - contracts/source/ethereum/CryptosToken.sol
    polygon
    CryptosTokenPolygon.sol - contracts/source/polygon/CryptosTokenPolygon.sol

    Disclaimer