Web3 · Smart Contract Audit

DIA Security Audits

softstack has completed 12 smart contract audits for DIA between August 2020 and February 2022, reporting 18 findings in total (1 medium, 7 low and 10 informational). Every report is published in the softstack public audit archive.

Key facts

Client
DIA
Audits completed
12
First audited
Latest audit
Languages
Solidity
Market cap
$20M as of 2026-09-30

About the project

DIA is an open-source oracle network that delivers verifiable price and asset data to onchain applications. It sources trade data directly from centralised and decentralised exchanges and publishes feeds whose methodology can be audited from source to chain. Coverage spans digital assets, tokenised real-world assets, reserve data and onchain randomness across many blockchains.

Findings

Combined across all 12 reviews softstack has completed for DIA. Each report is broken out below.

0Critical
0High
1Medium
7Low
10Informational

Reports

Newest first. Every report covers its own scope and commit.

  1. Oracle v2 on Arbitrum smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  2. Oracle v2 on Avalanche smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  3. Oracle v2 on Moonbeam smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  4. Oracle v2 on Polygon smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  5. DATA Oracle (Key Value) on Metis smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  6. DATA Oracle (Key Value) on Aurora smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  7. DATA Oracle (Key Value) on Fantom smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  8. DATA Oracle (Key Value) on Arbitrum smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  9. DATA Oracle (Key Value) on Avalanche smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational

    0 of 1 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    1 module
    1. See the published report for the file list
    All 1 findings
    IDTitleSeverityStatus
    5.1.1Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalacknowledged
  10. DATA Staking smart contract audit

    · 2 files

    PDF
    0Critical
    0High
    0Medium
    2Low
    0Informational

    2 of 2 resolved

    ScopeSource repositorygithub.com/diadata-org/diadata

    Components reviewed

    2 modules · 2 files
    1. contracts/DIAStaking.sol
    2. DIAStaking.sol
    All 2 findings
    IDTitleSeverityStatus
    5.1.1Wrong import of OpenZeppelin library

    Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are added directly into the

    Lowfixed
    5.1.2SPDX license identifier

    Code Snippet Result/Recommendation Warning: SPDX license identifier not provided in source file. Line NA Before publishing, consider adding a comment containing "SPDX-License-Identifier: <SPDX- License>" to each source file.

    Lowfixed
  11. Yield smart contract audit

    · 2 files

    PDF
    0Critical
    0High
    1Medium
    3Low
    1Informational
    Scope

    Components reviewed

    2 modules · 2 files
    1. Versionyield.sol
    2. yield.sol
  12. token smart contract audit

    · 1 file

    PDF
    0Critical
    0High
    0Medium
    2Low
    0Informational
    ScopeSource repositorygithub.com/gnosis/dex-liquidity-provision

    Components reviewed

    1 module · 1 file
    1. DIAToken.sol

About this engagement

A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.

How softstack runs smart contract audits

Methodology

Review process

  1. Scoping and threat modelling

    The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. Reporting

    Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.

  6. Remediation verification

    Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.

Standards and references

  • SWC RegistrySmart Contract Weakness Classification
  • CWECommon Weakness Enumeration

FAQ

DIA was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 12 smart contract audits for DIA between August 2020 and February 2022. The published reports are linked on this page and in the softstack public audit archive.

12 separate reviews, the first in August 2020 and the most recent in February 2022. Each one covers its own scope and commit, and is listed individually on this page.

18 findings across all 12 reviews: 1 medium, 7 low and 10 informational.

Each report covers the code as it stood at the commit it names, the most recent in February 2022. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.