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

Audit name:

[SCA] 3dotlink | ERC20 | Jan2024

Date:

Feb 11, 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 3dotlink team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

The 3dotlink serves as a versatile and integral utility within the 3dotlink platform, offering a range of functionalities that enhance the user experience, promote community engagement, and facilitate various interactions within the ecosystem.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20
Timeline18/01/2024 - 23/01/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/wasaamqazi/3DotLink→
    Commit6b6a6a69b00e7f1a5b080df245d8f450796637c7

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    100%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    3Total Findings
    3Resolved
    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 3dotlink
    Audited ByTurgay Arda Usman
    Approved By
    Websitehttps://www.3dotlink.io/→
    Changelog23/01/2024 - Preliminary Report
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for 3dotlink
      Audited By
      Turgay Arda Usman
      Approved By
      Changelog
      23/01/2024 - Preliminary Report

    System Overview

    3dotlink is a ERC20 project with the following contracts:

    ThreeDot  — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. Burning is allowed. Also has Pausable and Ownable functionality.

    It has the following attributes:

    • Name: Three Dot Link.

    • Symbol: 3DOT.

    • Decimals: 18.

    • Total supply: 1 bilion tokens.

    Privileged roles

    • The owner of the ThreeDot contract can pause and unpause the contract.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 10 out of 10.

    • Functional requirements are provided.

    • Technical requirements are provided.

    Code quality

    The total Code Quality score is 10 out of 10.

    • The code will be deployed via Remix.

    Test coverage

    Code coverage of the project is 100% (branch coverage) due to >250LOC.

    Security score

    Upon auditing, the code was found to contain 1 critical, 0 high, 1 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

    No risks provided.

    Findings

    F-2024-0543The contract does not depend on the latest version of the OpenZeppelin library
    Status
    fixed
    Severity

    Critical
    F-2024-0545Pausable punctionality is not documented
    Status
    fixed
    Severity

    Medium
    F-2024-0544Solidity compiler version is not locked
    Status
    fixed
    Severity

    Observation
    Code
    ―
    Title
    Status
    Severity
    F-2024-0543The contract does not depend on the latest version of the OpenZeppelin library
    fixed

    Critical
    F-2024-0545Pausable punctionality is not documented
    fixed

    Medium
    F-2024-0544Solidity compiler version is not locked
    fixed

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

    3DotLinkToken.sol - 3DotLinkToken.sol

    Disclaimer