Q2 2026 Security & Compliance Report67 incidents, $764M in losses, 88% from operational failures.
Get the report →
DOP (Data Ownership Protocol) logo

DOP (Data Ownership Protocol)

Audit name:

[SCA] DOP | ERC20 | Mar2024

Date:

Mar 27, 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 DOP (Data Ownership Protocol) team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

DOP is an ERC-20 token project that uses OpenZeppelin's token standars.

titlecontent
PlatformEVM
LanguageSolidity
TagsSolidity; Fungible Token
Timeline07/03/2024 - 08/03/2024
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/dop-labs/dop-token→
    Commit5cbcb15

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    87.5%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    1Total Findings
    0Resolved
    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 DOP (Data Ownership Protocol)
    Audited ByOlesia Bilenka
    Approved ByAtaberk Yavuzer
    Websitehttps://dop.org/→
    Changelog08/03/2024 - Preliminary Report

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for DOP (Data Ownership Protocol)
      Audited By
      Olesia Bilenka
      Approved By
      Ataberk Yavuzer
      Website
      https://dop.org/→
      Changelog
      08/03/2024 - Preliminary Report

    System Overview

    DOP — is an ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. The token is burnable and has permit functionality.

    It has the following attributes:

    • Name: DOP

    • Symbol: DOP

    • Decimals: 18

    • Total supply: Fixed

    The token is initially non-transferable, with transferring capabilities only becoming available to a predefined list of accounts, which the contract owner can modify. Once the owner enables transfers, this action is irreversible, making the token permanently transferable thereafter.

    Privileged roles

    • The DOP contract owner can edit the initial list of accounts allowed for token transfers and enable transferring, and transfer or renounce the contract ownership.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 10 out of 10.

    • The functional requirements are provided.

    • The technical description is provided.

    Code quality

    The total Code Quality score is 10 out of 10.

    • The code follows Solidity style guide.

    • The development environment is configured.

    Test coverage

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

    • Basic user interactions are covered with tests.

    • Some negative case coverage is missed.

    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.

    Scoring Methodologyarrow right

    Risks

    The DOP token's transferability is initially disabled and can only be enabled by the owner. Additionally, the owner controls the list of users initially permitted to transfer tokens.

    Findings

    F-2024-1376Redundant Variable Initialization to Zero
    Status
    unfixed
    Severity

    Observation
    Code
    ―
    Title
    Status
    Severity
    F-2024-1376Redundant Variable Initialization to Zero
    unfixed

    Observation
    1-1 of 1 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/dop-labs/dop-token→
    Commit5cbcb156be94db7cb6458271756c7b7f1067b88d
    WhitepaperHacken.io DOP Token Revised Content.pdf (sha-3: c18edba6189815bb00cb22fd0dc450268e9bdf4406cd28ac4a0725083c2e88f0)

    • Scope Details

      Repository
      https://github.com/dop-labs/dop-token→
      Commit
      5cbcb156be94db7cb6458271756c7b7f1067b88d
      Whitepaper
      Hacken.io DOP Token Revised Content.pdf (sha-3: c18edba6189815bb00cb22fd0dc450268e9bdf4406cd28ac4a0725083c2e88f0)

    Contracts in Scope

    contracts
    DOP.sol - contracts › DOP.sol

    Disclaimer