Introduction
We express our gratitude to the ChainGPT team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
The CGPT token is a utility token that is used to access various AI tools and products powered by ChainGPT. It plays a significant role in the ChainGPT ecosystem as it is required for users to access certain features and services within the platform.
| title | content |
|---|---|
| Platform | EVM |
| Language | Solidity |
| Tags | ERC20 |
| Timeline | 20/03/2023 - 03/04/2023 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Review Scope | |
|---|---|
| Repository | https://github.com/ChainGPT-org/CGPT_Token→ |
| Commit | 093b8dc |
Review Scope
- Commit
- 093b8dc
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 ChainGPT |
| Audited By | Hacken |
| Website | https://www.chaingpt.org/→ |
| Changelog | 03/04/2023 - Initial Review |
| 04/04/2023 - Second Review |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for ChainGPT
- Audited By
- Hacken
- Website
- https://www.chaingpt.org/→
- Changelog
- 03/04/2023 - Initial Review
- 04/04/2023 - Second Review
System Overview
The CGPT token is a utility token that is used to access various AI tools and products powered by ChainGPT. It plays a significant role in the ChainGPT ecosystem as it is required for users to access certain features and services within the platform. Users can obtain CGPT tokens through exchanges where it is listed or by participating in the ChainGPT token sale events.
The repository is composed by a single ERC20 contract:
ChainGPT — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. It has the following attributes:
Name: ChainGPT
Symbol: CGPT
Decimals: 18
Total supply: 1b tokens.
Privileged roles
The contract inherits Ownable, the deployer gets set as owner.
Executive Summary
Documentation quality
The total Documentation quality score is 10 out of 10.
Functional requirements are provided and complete.
Technical description is provided and complete.
Code quality
The total Code quality score is 10 out of 10.
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 2 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 10. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2023-0631 | Redundant Ownable | unfixed | Low | |
| F-2023-0630 | Floating Pragma | 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/ChainGPT-org/CGPT_Token→ |
| Commit | 093b8dc |
| Whitepaper | Not provided |
| Requirements | Provided→ |
| Technical Requirements | Provided→ |