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

Audit name:

[SCA] Wrapped Millix | Bridge + ERC20 | Mar2023

Date:

Mar 2, 2023

Table of Content

→Introduction
→Audit Summary
→Document Information
→System Overview
→Executive Summary
→Findings
→Appendix 1. Severity Definitions
→Appendix 2. Scope
→Disclaimer

Want a comprehensive audit report like this?

Introduction

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

Millix is an open source and fully decentralized cryptocurrency project. Designed for simplicity, transacts at very high speed and very large scale.

titlecontent
PlatformEthereum
LanguageSolidity
TagsERC20
Timeline10/02/2023 - 01/03/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/millix/millix-bridge-contract→
    Commit76a2dc84776e9881423bde9033f6f03fad385518

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    66.67%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    9Total Findings
    9Resolved
    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 Wrapped Millix
    Audited ByHacken
    Websitehttps://millix.org/→
    Changelog14/02/2023 – Initial Review
    01/03/2023 – Second Review
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Wrapped Millix
      Audited By
      Hacken
      Changelog
      14/02/2023 – Initial Review
      01/03/2023 – Second Review

    System Overview

    Millix is a ERC20 token with the following contract:

    WrappedMillix — simple ERC-20 token with additional features, including pause and resume, minting and burning, and vesting restrictions. It has the following attributes:

    • Name: WrappedMillix.

    • Symbol: WMLX.

    • Decimals: 1.

    • Total supply: 9,000,000,000,000,000 WMLX (nine quadrillion) tokens.

    Privileged roles

    • The owner of the WrappedMillix contract can pause, unpause the contract, and stop transfer, burn, mint processes for specific address or for all addresses.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 10 out of 10.

    • Functional requirements are provided.

    • Technical description is provided.

    Code quality

    The total Code quality score is 10 out of 10.

    • The development environment is configured.

    • The code follows the Solidity style guides.

    Test coverage

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

    • Deployment and basic user interactions are covered with tests.

    • Interactions by several users are not tested thoroughly.

    • Negative cases coverage is missed.

    Security score

    Upon auditing, the code was found to contain 0 critical, 2 high, 5 medium, and 2 low severity issues. Out of these, 9 issues have been addressed and resolved, 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.

    Findings

    F-2023-1436 Highly Permissive Role Access
    Status
    fixed
    Severity

    High
    F-2023-1435Requirements Violation
    Status
    fixed
    Severity

    High
    F-2023-144 Best Practice Violation
    Status
    fixed
    Severity

    Medium
    F-2023-144Missing Events
    Status
    fixed
    Severity

    Medium
    F-2023-143Best Practice Violation
    Status
    fixed
    Severity

    Medium
    F-2023-1438Tautology
    Status
    fixed
    Severity

    Medium
    F-2023-1437 Contradiction
    Status
    fixed
    Severity

    Medium
    F-2023-1443 Missing Empty String Check
    Status
    fixed
    Severity

    Low
    F-2023-144Floating Pragma
    Status
    fixed
    Severity

    Low
    Code
    ―
    Title
    Status
    Severity
    F-2023-1436 Highly Permissive Role Access
    fixed

    High
    F-2023-1435Requirements Violation
    fixed

    High
    F-2023-144 Best Practice Violation
    fixed

    Medium
    F-2023-144Missing Events
    fixed

    Medium
    F-2023-143Best Practice Violation
    fixed

    Medium
    F-2023-1438Tautology
    fixed

    Medium
    F-2023-1437 Contradiction
    fixed

    Medium
    F-2023-1443 Missing Empty String Check
    fixed

    Low
    F-2023-144Floating Pragma
    fixed

    Low
    1-9 of 9 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/millix/millix-bridge-contract→
    Commit76a2dc84776e9881423bde9033f6f03fad385518
    WhitepaperProvided→
    RequirementsProvided→
    Technical RequirementsProvided→

    Contracts in Scope

    contracts
    interfaces
    IMillixBridge.sol - contracts › interfaces › IMillixBridge.sol
    WrappedMillix.sol - contracts › WrappedMillix.sol

    Disclaimer