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

Audit name:

[SCA] BOLD | ERC20 | Mar2024

Date:

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

BOLD is an ERC-20 token project.

titlecontent
PlatformEVM
LanguageSolidity
TagsSolidity; Fungible Token
Timeline06/03/2024 - 24/07/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/we-are-bold/contracts→
    Commit0d32de1
    Remediation Commitca623f7

    Audit Summary

    Total9.8/10
    Security Score

    10/10

    Test Coverage

    70.83%

    Code Quality Score

    9/10

    Documentation Quality Score

    10/10

    5Total Findings
    4Resolved
    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 BOLD
    Audited ByOlesia Bilenka
    Approved ByAtaberk Yavuzer
    Websitehttps://wearebold.io→
    Changelog07/03/2024 - Preliminary Report
    18/03/2024 - Final Report
    26/07/2024 - Project Renaming
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for BOLD
      Audited By
      Olesia Bilenka
      Approved By
      Ataberk Yavuzer
      Changelog
      07/03/2024 - Preliminary Report
      18/03/2024 - Final Report
      26/07/2024 - Project Renaming

    System Overview

    BOLD is an ERC-20 token project with the following contracts:

    BOLD — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed.

    It has the following attributes:

    • Name: BOLD

    • Symbol: BOLD

    • Decimals: 18

    • Total supply: 100m tokens.

    ERC20 — a contract that provides basic functionality for the BOLD contract.

    SafeMath — a library that provides wrappers over Solidity's arithmetic operations with added overflow checks. Used in the ERC20 contract.

    Context — a contract that provides information about the current execution context. Used in the ERC20 contract.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 10 out of 10.

    • The requirements and tokenomics are provided.

    Code quality

    The total Code Quality score is 9 out of 10.

    • The code duplicates commonly known contracts instead of reusing them.

    • The development environment is configured.

    • The code mostly follows Solidity style guide.

    Test coverage

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

    • Most of the functionality is covered with tests.

    • Some utils and main functionality conditions are not tested thoroughly.

    Security score

    Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 0 low and 5 informational 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 9.8. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Risks

    The whitepaper refers to the project under its previous name before the renaming occurred.

    Findings

    F-2024-1310Redundant Constructor Visibility
    Status
    fixed
    Severity

    Observation
    F-2024-1308Variables to Mark as Immutable or Constants
    Status
    fixed
    Severity

    Observation
    F-2024-1307Redundant SafeMath library usage
    Status
    fixed
    Severity

    Observation
    F-2024-1305 Redundant Ownable Inheritance
    Status
    accepted
    Severity

    Observation
    F-2024-1300Floating Pragma
    Status
    fixed
    Severity

    Observation
    Code
    ―
    Title
    Status
    Severity
    F-2024-1310Redundant Constructor Visibility
    fixed

    Observation
    F-2024-1308Variables to Mark as Immutable or Constants
    fixed

    Observation
    F-2024-1307Redundant SafeMath library usage
    fixed

    Observation
    F-2024-1305 Redundant Ownable Inheritance
    accepted

    Observation
    F-2024-1300Floating Pragma
    fixed

    Observation
    1-5 of 5 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

    BOLD.sol - BOLD.sol
    interfaces
    IERC20.sol - interfaces › IERC20.sol
    libraries
    SafeMath.sol - libraries › SafeMath.sol
    utility
    Context.sol - utility › Context.sol
    Ownable.sol - utility › Ownable.sol

    Disclaimer