Introduction
We express our gratitude to the Letstop team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
The Letstop platform is dedicated to enhancing road safety by incentivizing driver safer driving behaviors with a unique rewards system.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 26/03/2024 - 27/03/2024 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/LETSTOPdev/STOPToken→ |
| Commit | 6a137f2 |
Review Scope
- Repository
- https://github.com/LETSTOPdev/STOPToken→
- Commit
- 6a137f2
Audit Summary
10/10
0%
10/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 Letstop |
| Audited By | Philipp Eder |
| Approved By | Yves Toiser |
| Website | https://hacken.io→ |
| Changelog | 26/03/2024 - Preliminary Report & 03/04/2024 Final Report |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Letstop
- Audited By
- Philipp Eder
- Approved By
- Yves Toiser
- Website
- https://hacken.io→
- Changelog
- 26/03/2024 - Preliminary Report & 03/04/2024 Final Report
System Overview
The Letstop repository contains the following contract:
STOPToken — simple ERC-20 token with a limited supply that allows minting only for the owner of the contract.
It has the following attributes:
Name: STOP
Symbol: STOP
Decimals: 18
Total supply: 100 Million tokens.
Privileged roles
The owner of the contract can mint any amount of tokens up to the supply cap of 100 Million tokens to any address.
Executive Summary
Documentation quality
The total Documentation Quality score is 10 out of 10.
Functional requirements are provided.
Technical description is provided.
Code quality
The total Code Quality score is 10 out of 10.
Test coverage
Code coverage of the project is 0% (branch coverage).
Security score
Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 0 low severity issues, 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 owner of the contract has the sole privilege to mint any amount of tokens up to the supply cap of 100 Million tokens to any address.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2024-1733 | The code duplicates commonly known contracts instead of reusing them | accepted | Observation | |
| F-2024-1732 | Missing zero value checks for mint() and batchMint() | fixed | Observation | |
| F-2024-1731 | Solidity Style Guide violation | fixed | Observation | |
| F-2024-1730 | Missing zero address check in constructor | fixed | Observation | |
| F-2024-1689 | Functions not used internally can be marked as external | fixed | Observation | |
| F-2024-1686 | 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/LETSTOPdev/STOPToken→ |
| Commit | 6a137f25ae5473d758d2ca85d51667830f4c0d67 |
| Whitepaper | - |
| Requirements | Requirements.pdf→ |
| Technical Requirements | README.md→ |
Scope Details
- Repository
- https://github.com/LETSTOPdev/STOPToken→
- Commit
- 6a137f25ae5473d758d2ca85d51667830f4c0d67
- Whitepaper
- -
- Requirements
- Requirements.pdf→
- Technical Requirements
- README.md→