Audit name:
[SCA] CoinPays | Token Audit | May2024
Date:
Jun 11, 2024
Table of Content
Introduction
We express our gratitude to the CoinPays team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
CoinPays is an ARC-20 token contract.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | Solidity, ARC-20 |
| Timeline | 27/05/2024 - 28/05/2024 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/CoinPaysIO/token-smart-contract→ |
| Commit | 3300f87 |
| Remediation Commit | 3c2e984 |
Review Scope
- Commit
- 3300f87
- Remediation Commit
- 3c2e984
Audit Summary
10/10
0%
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 CoinPays |
| Audited By | Olesia Bilenka |
| Approved By | Ataberk Yavuzer |
| Website | https://coinpays.io/→ |
| Changelog | 27/05/2024 - Preliminary Report |
| 28/05/2024 - Final Report |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for CoinPays
- Audited By
- Olesia Bilenka
- Approved By
- Ataberk Yavuzer
- Website
- https://coinpays.io/→
- Changelog
- 27/05/2024 - Preliminary Report
- 28/05/2024 - Final Report
System Overview
CoinPays is an ARC-20 project with the following contracts:
CoinPays - is a simple ARC-20 token that mints 100000000 tokens to a deployer. Additional minting is not allowed. The name. symbol, decimals are defined during deployment.
Ownable - is a contract ithat designates an account (usually the contract deployer) as the owner with exclusive access to specific functions.
Context - is a contract that provides information about the current execution context, such as the sender of the transaction and its data.
Privileged roles
The owner of the CoinPays and Ownable contract can transfer and renounce ownership.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are provided.
Technical description is provided.
Development environment description is provided.
Code quality
The total Code quality score is 9 out of 10.
The contracts and interfaces of the project are not separated into individual files and are contained within a single file.
The code mostly follows best practices and style guides.
The development environment is configured.
Test coverage
Code coverage of the project is 0% (branch coverage).
Tests are not provided.
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 1 low severity issues. Out of these, 1 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
No certain risks were specified for given contract(s).
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2024-3312 | Missing Balance and Allowance Verification in Transfers Causing Underflow Errors | fixed | Low | |
| F-2024-3317 | Incorrect Error Message in Token Transfers | fixed | Observation | |
| F-2024-3315 | Redundant Constructor in the Context Contract | fixed | Observation | |
| F-2024-3314 | Redundant Ownable Inheritance Leading to Extra Gas Usage During Deployment | accepted | Observation | |
| F-2024-3311 | Floating Pragma | fixed | Observation |
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/CoinPaysIO/token-smart-contract→ |
| Commit | 3300f87b2678e0c53e6d2a7e80dbe99bb1f05f9b |
| Whitepaper | https://github.com/CoinPaysIO/token-smart-contract/blob/main/docs/general.md→ |
Scope Details
- Commit
- 3300f87b2678e0c53e6d2a7e80dbe99bb1f05f9b