Chat AI
0xa89Bf95c5f15a847c8Eb8D348cd7feD719AD7D80 0xa89B...AD7D80

Static analysis Dynamic analysis Symbolic Execution SWC check

ChatAI, make life full of AI, talk to AI in the web page, in the telegram, in all chat tools, and AI answers any answer you need to know. This is AI, ChatAI.

Contract address
0xa89B...AD7D80
Network Ethereum Mainnet
License MIT
Compiler v0.8.18 v0.8.18+commit.87f61d96
Type N/A
Language Solidity
Request date 2023/03/20
Revision date 2023/03/20
Critical
Passed
High
Passed

Owner privileges

Crucial issues found The contract does contain issues of high or medium criticality. In some circumstances, the Contract may not function as intended and may pose a safety risk.
Contract owner cannot mint It is not possible to mint new tokens.
Contract owner cannot blacklist addresses. It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Contract cannot be locked Owner cannot lock any user funds.
Token cannot be burned There is no burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
Comments

Owner privileges

  • set liquidityPool
  • set marketingPool

 

Audit Scope

This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.

We will verify the following claims:
  • Correct implementation of Token standard
  • Deployer cannot mint any new tokens
  • Deployer cannot burn or lock user funds
  • Deployer cannot pause the contract
  • Overall checkup (Smart Contract Security)
The auditing process follows a routine series of steps:
  • Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
  • Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  • Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  • Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  • Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
  • Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
  • Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.

Functions
public

0

State variables
public

0

Total lines
of code

132

Capabilities
Hover on items

Functions
public

8

State variables
public

0

Total lines
of code

250

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

56

Capabilities
Hover on items

Functions
public

0

State variables
public

0

Total lines
of code

27

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

63

Capabilities
Hover on items

Functions
public

6

State variables
public

0

Total lines
of code

75

Capabilities
Hover on items

Functions
public

5

State variables
public

3

Total lines
of code

82

Capabilities
Hover on items

Audit Details

Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.

Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.

medium Issues

Pending

#1 Issue

Owner can drain out contract tokens

Token.sol

L37

Description

Anyone is able to pass own contract address to take out the whole token balance of own contract. After it marketingpool wallet can sell it and rug the contract. Be aware of it and do your own research.

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

ERC20.sol

L66

L225

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

Token.sol

L46

Description

Check that the address is not zero.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

SafeMath.sol

L103-105

L120-131

L79-90

L44-46

Description

Remove unused functions.

Pending

#2 Issue

Functions that are not used (dead-code)

ERCContext.sol

L23-26

Description

Remove unused functions.

Pending

#3 Issue

Functions that are not used (dead-code)

ERC20.sol

L203-209

L242-249

L184-190

Description

Remove unused functions.

Pending

#4 Issue

Functions that are not used (dead-code)

Token.sol

L75-77

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

Public function that could be declared external (external-function)

ERC20.sol

L39-41

L46-48

L58-61

L66-68

L77-80

L94-106

L120-123

L139-146

Description

Use the `external` attribute for functions never called from the contract.

Pending

#2 Issue

Public function that could be declared external (external-function)

ERC20Detailed.sol

L29-31

L37-39

L53-55

Description

Use the `external` attribute for functions never called from the contract.

Pending

#3 Issue

Public function that could be declared external (external-function)

ERCOwnable.sol

L30-32

L49-52

L58-62

Description

Use the `external` attribute for functions never called from the contract.

Diagrams

Disclaimer

SolidProof.io reports are not, nor should be considered, an “endorsement” or “disapproval” of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any “product” or “asset” created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...)

SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.

SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProof’s position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.