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

Audit name:

[SCA] Destra | ERC20 | Aug2024

Date:

Aug 29, 2024

Table of Content

→Introduction
→Audit Summary
→System Overview
→Risks
→Findings
→Appendix 1. Severity Definitions
→Appendix 2. Scope
→Disclaimer

Want a comprehensive audit report like this?

Introduction

We express our gratitude to the Destra Network team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

Destra Network provides a comprehensive suite of decentralized solutions, including decentralized cloud infrastructure, AI computing, decentralized storage solutions, decentralized database, and decentralized DNS.

Document

NameSmart Contract Code Review and Security Analysis Report for Destra Network
Audited ByAndy Cho
Approved ByGrzegorz Trawinski
Websitehttps://destra.network→
Changelog23/08/2024 - Preliminary Report
29/08/2024 - Final Report
PlatformEthereum
LanguageSolidity
TagsToken
Methodologyhttps://hackenio.cc/sc_methodology→
  • Document

    Name
    Smart Contract Code Review and Security Analysis Report for Destra Network
    Audited By
    Andy Cho
    Approved By
    Grzegorz Trawinski
    Changelog
    23/08/2024 - Preliminary Report
    29/08/2024 - Final Report
    Platform
    Ethereum
    Language
    Solidity
    Tags
    Token

Review Scope

Repositoryhttps://github.com/DestraNetwork/DSync→
Commit804d9ca

Audit Summary

5Total Findings
5Resolved
0Accepted
0Mitigated

The system users should acknowledge all the risks summed up in the risks section of the report

Documentation quality

  • Functional requirements are provided.

  • Technical description is provided.

Code quality

  • The development environment is configured.

Test coverage

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

  • Deployment and basic user interactions are covered with tests.

  • Negative cases coverage is missed.

System Overview

DestraNetwork  — ERC-20 token with a tax included on purchases and sales.

Privileged roles

  • The owner of the contract can addLiquidityPool, setSwapBackRateLimit, setTxLimit, setMaxWallet, setIsFeeExempt, setFees, and setFeeReceivers.

Risks

Centralized Control of Setting Fee Rates: The token contract's design allows for centralized control over setting fee rates, potentially undermining trust in the project's economic governance.

Findings

F-2024-5507Should Revert or Emit an Event If The Transfer to Marketing Wallet Is Failed
Status
fixed
Severity

Low
F-2024-5500blacklistCount Does Not Match The Actual Number Of Blacklisted Wallets
Status
fixed
Severity

Low
F-2024-5506Missing Zero Address Validation
Status
fixed
Severity

Observation
F-2024-5504Missing Events For Key Value Updates
Status
fixed
Severity

Observation
F-2024-5501State Variables That Should Be Constant
Status
fixed
Severity

Observation
Code
―
Title
Status
Severity
F-2024-5507Should Revert or Emit an Event If The Transfer to Marketing Wallet Is Failed
fixed

Low
F-2024-5500blacklistCount Does Not Match The Actual Number Of Blacklisted Wallets
fixed

Low
F-2024-5506Missing Zero Address Validation
fixed

Observation
F-2024-5504Missing Events For Key Value Updates
fixed

Observation
F-2024-5501State Variables That Should Be Constant
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:

Scope Details

Repositoryhttps://github.com/DestraNetwork/DSync→
Commit804d9ca733b37bc0f891e8ab8c8fac49151ce55c
Whitepaperhttps://destra-network.gitbook.io/documentation→
Technical RequirementsTECHNICAL_DESCRIPTION.md
Functional RequirementsREQUIREMENTS.md

Contracts in Scope

contracts
DestraNetwork.sol - contracts › DestraNetwork.sol

Disclaimer