Web3 · Smart Contract Audit

Curate Security Audits

softstack has completed 3 smart contract audits for Curate between February 2021 and April 2022, reporting 6 findings in total (1 high, 3 low and 2 informational), of which 2 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.

Key facts

Client
Curate
Audits completed
3
First audited
Latest audit
Languages
Solidity

About the project

Curate is a marketplace application that uses blockchain rails for payments and returns rewards to buyers and sellers on transactions. The marketplace lists both physical and digital goods, including electronics, clothing, gaming items and NFTs. Its contracts were deployed on Ethereum and BNB Chain and reviewed in a smart contract audit in 2022.

Findings

Combined across all 3 reviews softstack has completed for Curate. Each report is broken out below.

0Critical
1High
0Medium
3Low
2Informational

2 of 6 findings resolved before the final reports.

Reports

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

  1. XCUR Token (BSC) smart contract audit

    · 1 file

    PDF
    0Critical
    0High
    0Medium
    2Low
    1Informational

    1 of 3 resolved

    Scope

    Components reviewed

    1 module · 1 file
    1. XCUR.sol
    All 3 findings
    IDTitleSeverityStatus
    5.2.1Extensive Owner rights

    Code Snippet Result/Recommendation The owner has extensive rights. The auditor has not recognized any multi-sig structure.

    Lowfixed
    5.2.2Missing 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.

    Lowacknowledged
    5.2.3A floating pragma is set.

    Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.8.9". It is recommended to specify a fixed compiler version to

    Informationalacknowledged
  2. XCUR Token (ETH) smart contract audit

    · 1 file

    PDF
    0Critical
    1High
    0Medium
    1Low
    1Informational

    1 of 3 resolved

    Scope

    Components reviewed

    1 module · 1 file
    1. XCUR.sol
    All 3 findings
    IDTitleSeverityStatus
    5.2.1Extensive Owner rights

    Code Snippet Result/Recommendation The owner has extensive rights. The auditor has not recognized any multi-sig structure.

    Highfixed
    5.2.2Missing 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.

    Lowacknowledged
    5.2.3A floating pragma is set.

    Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.8.9". It is recommended to specify a fixed compiler version to

    Informationalacknowledged
  3. XCUR Token (curate.style) smart contract audit

    · 1 file

    PDF
    0Critical
    0High
    0Medium
    0Low
    0Informational

    No security findings reported.

    Scope

    Components reviewed

    1 module · 1 file
    1. xcur_token.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

Curate 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 3 smart contract audits for Curate between February 2021 and April 2022. The published reports are linked on this page and in the softstack public audit archive.

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

6 findings across all 3 reviews: 1 high, 3 low and 2 informational. 2 of 6 were resolved or mitigated before the final reports.

Each report covers the code as it stood at the commit it names, the most recent in April 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.