Introduction
We express our gratitude to the 3dotlink team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
The 3dotlink serves as a versatile and integral utility within the 3dotlink platform, offering a range of functionalities that enhance the user experience, promote community engagement, and facilitate various interactions within the ecosystem.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 18/01/2024 - 23/01/2024 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/wasaamqazi/3DotLink→ |
| Commit | 6b6a6a69b00e7f1a5b080df245d8f450796637c7 |
Review Scope
- Repository
- https://github.com/wasaamqazi/3DotLink→
- Commit
- 6b6a6a69b00e7f1a5b080df245d8f450796637c7
Audit Summary
10/10
100%
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 3dotlink |
| Audited By | Turgay Arda Usman |
| Approved By | |
| Website | https://www.3dotlink.io/→ |
| Changelog | 23/01/2024 - Preliminary Report |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for 3dotlink
- Audited By
- Turgay Arda Usman
- Approved By
- Website
- https://www.3dotlink.io/→
- Changelog
- 23/01/2024 - Preliminary Report
System Overview
3dotlink is a ERC20 project with the following contracts:
ThreeDot — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. Burning is allowed. Also has Pausable and Ownable functionality.
It has the following attributes:
Name: Three Dot Link.
Symbol: 3DOT.
Decimals: 18.
Total supply: 1 bilion tokens.
Privileged roles
The owner of the ThreeDot contract can pause and unpause the contract.
Executive Summary
Documentation quality
The total Documentation Quality score is 10 out of 10.
Functional requirements are provided.
Technical requirements are provided.
Code quality
The total Code Quality score is 10 out of 10.
The code will be deployed via Remix.
Test coverage
Code coverage of the project is 100% (branch coverage) due to >250LOC.
Security score
Upon auditing, the code was found to contain 1 critical, 0 high, 1 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
No risks provided.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2024-0543 | The contract does not depend on the latest version of the OpenZeppelin library | fixed | Critical | |
| F-2024-0545 | Pausable punctionality is not documented | fixed | Medium | |
| F-2024-0544 | Solidity compiler version is not locked | 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/wasaamqazi/3DotLink→ |
| Commit | 6b6a6a69b00e7f1a5b080df245d8f450796637c7 |
| Whitepaper | https://3dotlink.gitbook.io/3dotlink-whitepaper/→ |
| Requirements | https://3dotlink.gitbook.io/3dotlink-whitepaper/tokenomics/utility-token-usd3dot→ |
| https://github.com/wasaamqazi/3DotLink/blob/main/README.md→ | |
| Technical Requirements | NatSpec comments. |
Scope Details
- Repository
- https://github.com/wasaamqazi/3DotLink→
- Commit
- 6b6a6a69b00e7f1a5b080df245d8f450796637c7
- Technical Requirements
- NatSpec comments.