Q1 2026 Security & Compliance Report44 incidents, $482M in losses, insights from 11 industry leaders.
Read the report
Aeternus Foundation Corporation logo

Aeternus Foundation Corporation

Audit name:

[SCA] Aeternus Foundation | ERC20 | Apr2023

Date:

Apr 13, 2023

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 Aeternus Foundation Corporation team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

Aeternus Foundation Corporation is a mixed-purpose system on a mission to bring Cryptocurrency to the Forefront of Everything.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20
Timeline07/04/2023 - 14/04/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/aeternusfoundation/ATRNO-Token→
    Commitbf21c8aa

    Audit Summary

    Total9.4/10
    Security Score

    10/10

    Test Coverage

    0.00%

    Code Quality Score

    7/10

    Documentation Quality Score

    10/10

    4Total Findings
    0Resolved
    0Accepted
    3Mitigated

    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 Aeternus Foundation Corporation
    Audited ByHacken
    Websitehttps://aeternus.foundation→
    Changelog14/04/2023 - Initial Review
    14/04/2023 - Second Review

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Aeternus Foundation Corporation
      Audited By
      Hacken
      Website
      https://aeternus.foundation→
      Changelog
      14/04/2023 - Initial Review
      14/04/2023 - Second Review

    System Overview

    Aeternus Foundation Corporation is a mixed-purpose system with the following contracts:

    Atrno — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed.

    It has the following attributes:

    • Name: ATRNO

    • Symbol: ATRNO

    • Decimals: 18

    • Total supply: 1b tokens.

    Privileged roles

    • No privileged roles.

    Recommendations

    • Create a development environment using Hardhat or Foundry frameworks. Add deployment scripts and tests.

    • We recommend using a Multi-Sig wallet with 3/5 signatures to store ATRNO token.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 10 out of 10.

    • Whitepaper is provided.

    • Functional requirements are present.

    • Technical documentation of the ERC20 token is provided.

    Code quality

    The total Code quality score is 7 out of 10.

    • Outdated Solidity version.

    • The development environment is not configured.

    • Best practice violations.

    Test coverage

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

    • Tests are not provided.

    Security score

    Upon auditing, the code was found to contain 0 critical, 0 high, 1 medium, and 3 low severity issues. Out of these, 0 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 9.4. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Scoring Methodologyarrow right

    Risks

    Most of the token supply is stored on project EOA wallets, the security of those wallets cannot be guaranteed. We recommend using a Multi-Sig wallet with 3/5 signatures.

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2023-0057Copy of Well-Known Contracts
    mitigated

    Medium
    F-2023-0060Missing SPDX License Identifier
    unfixed

    Low
    F-2023-0059Outdated Solidity Version
    mitigated

    Low
    F-2023-0058Floating Pragma
    mitigated

    Low
    1-4 of 4 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/aeternusfoundation/ATRNO-Token→
    Commitbf21c8aa
    WhitepaperProvided→
    RequirementsProvided→
    Technical RequirementsProvided→

    Contracts in Scope

    atrno.sol - atrno.sol

    Disclaimer