- Hacken
- Audits
- autominingtoken
- [SCA] AutoMiningToken | Liquidity Pool | Jun2023
Audit name:
[SCA] AutoMiningToken | Liquidity Pool | Jun2023
Date:
Sep 17, 2023
Table of Content
Introduction
We express our gratitude to the AutoMiningToken team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
AutoMiningToken (AMT) is a native token on the BNB Smart Chain network with a mission to democratize Bitcoin mining.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | Liquidity Pool; ERC20 |
| Timeline | 08/06/2023 - 20/09/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/AutoMiningToken/amtEnviroment→ |
| Commit | c674d1fcd1a3c6e1dd442d9407a5c789df8de9f3 |
Review Scope
- Commit
- c674d1fcd1a3c6e1dd442d9407a5c789df8de9f3
Audit Summary
10/10
100%
9/10
10/10
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 | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for AutoMiningToken |
| Audited By | Hacken |
| Website | https://www.autominingtoken.com/→ |
| Changelog | 15/06/2023 - Initial Review |
| 01/08/2023 - Second Review | |
| 29/08/2023 - Third Review | |
| 20/09/2023 - Fourth Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for AutoMiningToken
- Audited By
- Hacken
- Changelog
- 15/06/2023 - Initial Review
- 01/08/2023 - Second Review
- 29/08/2023 - Third Review
- 20/09/2023 - Fourth Review
System Overview
AutoMiningToken is a platform that allows, through its token - AMT, investment in BTC mining projects. Users who own AMT will be able to profit from the returns generated by the project based on the amount of AMT they own on all circulating tokens.
AMT — a simple ERC-20 token that does not mint any initial supply, but additional minting is allowed. Total supply is capped to 100 million tokens. It has the following attributes:
Name: AutoMiningToken
Symbol: AMT
Decimals: 18
Total supply: 100m tokens.
LiquidityAmt — a simple ERC-20 token to be used for liquidity purposes that does not mint any initial supply, but additional minting is allowed. It has the following attributes:
Name: liqAutoMiningToken
Symbol: liqAMT
Decimals: 18
Total supply: Infinite.
Market — a contract that allows users to withdraw USDT tokens against their AMT balance (a sort of liquidation operation), as well as buy AMT with USDT tokens.
Master — a contract that manages the liquidity pools and distributes rewards for liquidity providers and AMT token holders. Each reward charge is tracked through a snapshot mechanism. When the owner calls the "payRent" function, the reward for that specific moment will be distributed based on the snapshot of how many tokens they currently hold or how much they have utilized for the liquidity pool. So, the total reward amount and the timing of its distribution will depend on the system owner.
BurnVault — a contract that allows users to burn their AMT tokens in exchange for some amount of BTCB balance in the contract.
Privileged roles
The owner of the AMT contract can:
take snapshots
mint tokens
The owner of the LIQUIDITYAMT contract can:
take snapshots
mint tokens
The owner of the marketvault can:
set the Master contract address
transfer the backing tokens to itself
The owner of Master can:
extend the approval amount for addrRouter
set the payer wallet
add liquidity to be locked for 2 years
mint AMT tokens
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are provided.
Technical description is provided.
NatSpec is sufficient.
Code quality
The total Code quality score is 9 out of 10.
Development environment is configured.
Solidity Style Guides are not followed.
Test coverage
Code coverage of the project is 100% (branch coverage).
Security score
Upon auditing, the code was found to contain 1 critical, 2 high, 6 medium, and 4 low severity issues. Out of these, 13 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.8. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Risks
The system owner can mint an infinite amount of liqAMT tokens.
In the Market contract, AMT price to buy with USDT is specified by a centralized mechanism and can be changed by the system owner.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-0593 | Invalid Calculations | fixed | Critical | |
| F-2023-0595 | Invalid Calculations | fixed | High | |
| F-2023-0594 | Contradiction in Docs | fixed | High | |
| F-2023-0601 | Accumulation of Dust Values | fixed | Medium | |
| F-2023-0600 | Missing Validation | fixed | Medium | |
| F-2023-0599 | Highly Permissive Role Access | fixed | Medium | |
| F-2023-0598 | Missing Event Emitting | fixed | Medium | |
| F-2023-0597 | Best Practice Violation / Unchecked Return Value | fixed | Medium | |
| F-2023-0596 | Missing Validation | fixed | Medium | |
| F-2023-0605 | Invalid Hardcoded Value | fixed | Low |
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 | |
|---|---|
| Repository | https://github.com/AutoMiningToken/amtEnviroment→ |
| Commit | c674d1fcd1a3c6e1dd442d9407a5c789df8de9f3 |
| Whitepaper | Provided→ |
| Requirements | Provided→ |
| Technical Requirements | Not provided |