Q1 2025 Web3 Security ReportAccess control failures led to $1.63 billion in losses
Discover report insights
  • Hacken
  • Audits
  • linqai
  • [SCA] LinqAI / ERC20 + Staking / Mar2024

LinqAI

Audit name:

[SCA] LinqAI / ERC20 + Staking / Mar2024

Date:

Apr 19, 2024

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

LinqAI stands at the intersection of AI and Web3, driving transformative solutions that redefine how businesses operate in the decentralized economy. The core mission is to leverage the unparalleled potential of AI to enhance and streamline business processes, offering a direct pathway to efficiency, scalability, and profitability in the Web3 era.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20, Staking
Timeline25/03/2024 - 28/03/2024
Methodologyhttps://hackenio.cc/sc_methodology

    Review Scope

    Repositoryhttps://github.com/MonkeWriteCode/lnq-web3
    Commitfd3fca878f270bb9750924c4d186de4b76ca64f3

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    n/a

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    6Total Findings
    4Resolved
    2Accepted
    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 LinqAI
    Audited ByGrzegorz Trawinski
    Approved ByAtaberk Yavuzer
    Websitehttp://linqai.com/
    Changelog26/03/2024 - Preliminary Report
    28/03/2024 - Final Report
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for LinqAI
      Audited By
      Grzegorz Trawinski
      Approved By
      Ataberk Yavuzer
      Changelog
      26/03/2024 - Preliminary Report
      28/03/2024 - Final Report

    System Overview

    The LNQFarm contract is a staking solution that allows users to accrue staking rewards in LNQToken.

    Privileged roles

    • The owner of the LNQFarm has no privileged actions implemented.

    Executive Summary

    Documentation quality

    The total Documentation Quality score is 10 out of 10.

    Code quality

    The total Code Quality score is 10 out of 10.

    Test coverage

    Tests are not mandatory for the code less than 250 LOC.

    Security score

    Upon auditing, the code was found to contain 0 critical, 1 high, 0 medium, and 1 low severity issues, leading to a security score of 5 out of 10.  Within the retest phase all findings were fixed, 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.

    Risks

    The LNQToken tokens must be manually transferred to the LNQFarm in prior to enable rewards withdrawal.

    Findings

    Code
    Title
    Status
    Severity
    F-2024-1728First staker can get enourmous profits with small stake
    fixed

    High
    F-2024-1724 Lack of two-step ownership transfer
    fixed

    Low
    F-2024-1746Redundant Ownable inheritance
    accepted

    Observation
    F-2024-1727Return value of ERC20 transfer is not checked
    accepted

    Observation
    F-2024-1726Inconsistent Solidity pragma declaration
    fixed

    Observation
    F-2024-1725The compound() function has redundant calculations
    fixed

    Observation
    1-6 of 6 findings

    Identify vulnerabilities in your smart contracts.

    Appendix 1. Severity Definitions

    When auditing smart contracts, Hacken uses 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:

    Contracts in Scope

    contracts
    LNQFarm.sol - contracts/LNQFarm.sol
    access
    FarmOwner.sol - contracts/access/FarmOwner.sol

    Disclaimer