TRUST Summit | Nov 3, 2025 | NYCWhere decision-makers define the next chapter of secure blockchain adoption.
Learn more

SwissBorg

Audit name:

[SCA] SwissBorg | ERC20 | Aug2023

Date:

Aug 22, 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 Swissborg team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

SwissBorg’s objective is to create a democratic, decentralised and professional ecosystem to manage your portfolio of crypto assets.

titlecontent
PlatformEthereum, Solana, Polygon, Avalanche
LanguageSolidity
TagsERC20
Timeline20/06/2023 - 22/08/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/SwissBorg/borg-token→
    Commit77e8cb635040d3b8d9c3cf9217f3648ca037baee

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    100%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    6Total Findings
    4Resolved
    0Accepted
    2Mitigated

    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 Swissborg
    Audited ByHacken
    Websitehttps://swissborg.com/→
    Changelog27/06/2023 – Initial Review
    05/07/2023 - Second Review
    22/08/2023 - Third Review

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for Swissborg
      Audited By
      Hacken
      Website
      https://swissborg.com/→
      Changelog
      27/06/2023 – Initial Review
      05/07/2023 - Second Review
      22/08/2023 - Third Review

    System Overview

    SwissBorgToken is a Solidity smart contract that implements the new BORG token. It is based on the ERC20 standard and incorporates additional functionality from the ERC20Burnable, ERC20Permit, and ERC20Votes extensions provided by the OpenZeppelin library. Initial supply of new BORG is 1 billion tokens minus CHSB (old BORG) tokens sent to address(0) (to not mint tokens that cannot be migrated).

    ChsbToBorgMigrator is a Solidity smart contract that facilitates the migration process from the CHSB token to the BORG token. ChsbToBorgMigrator utilizes various libraries from the OpenZeppelin framework, including OwnableUpgradeable for managing ownership, PausableUpgradeable for pausing and unpausing contract operations, and UUPSUpgradeable for transparent contract upgrades.

    Privileged roles

    ChsbToBorgMigrator contract has 2 defined role:

    • owner - role assigned using OpenZeppelin OwnableUpgradeable library. Address with this role can change the address of a manager role.

    • manager - role assigned with Smart Contract variable. Address with this role can pause and unpause contract.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 10 out of 10.

    • Technical description is robust.

    • Functional requirements are detailed.

    Code quality

    The total Code quality score is 10 out of 10.

    • Code does not contain any code quality violation.

    Test coverage

    Code coverage of the project is 100% (branch coverage), with a mutation score of 63.44%.

    • Deployment and basic user interactions are covered with tests.

    • Negative cases coverage is present.

    Security score

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

    Scoring Methodologyarrow right

    Risks

    The system currently lacks the implementation of the AccessControlUpgradeable library provided by OpenZeppelin for the purpose of managing two distinct roles within the system. Presently, the system relies on the usage of the OwnableUpgradeable library to handle the owner role, while a custom mechanism has been devised to manage the manager role

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2023-1677 Copy Of Well Known Contract
    mitigated

    Medium
    F-2023-167Unused Variable
    mitigated

    Low
    I-2023-0428Use of Hard-Coded Values
    fixed

    Observation
    I-2023-0427Invalid Unit
    fixed

    Observation
    I-2023-0426Style Guide Violation
    fixed

    Observation
    I-2023-0425Public Functions That Should Be External
    fixed

    Observation
    1-6 of 6 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/SwissBorg/borg-token→
    Commit77e8cb635040d3b8d9c3cf9217f3648ca037baee
    WhitepaperNot provided
    RequirementsProvided→
    Technical RequirementsProvided

    Contracts in Scope

    contracts
    ChsbToBorgMigrator.sol - contracts › ChsbToBorgMigrator.sol
    SwissBorgToken.sol - contracts › SwissBorgToken.sol

    Disclaimer