TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

79.90
Poor Excellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x6b6d...E6B1
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/09/24
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

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.

Token transfer can be locked

Owner can lock user funds with owner functions.

Token cannot be burned

There is no burning within the contract without any allowances

Ownership is not renounced

Contract can be manipulated by owner functions.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


  • We recommend you to remove SafeMath and use raw mathematical operations
  • Liquidity will be added to the owner. Be aware of this because the owner can take out the liquidity anytime

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 3 findings

Pending

#1 medium Issue
Regain ownership
CoinToken.sol
L223-236
Description

"Owner can regain ownership after transferring it with following steps: Call lock function to set _previousOwner to the own address Call unlock function to get ownership back Transfer/renounce ownership Call unlock function to get ownership back Make sure to set the _previousOwnership back to address zero after using the unlock function"

Pending

#2 medium Issue
Fee's can be set over 100% and lock user funds
CoinToken.sol
-
Description

All fee's can be set without any limitation. If the fees are set over it by the owner, the user funds can be locked. We recommend you to implement a restriction to the set fee functions to make sure that the variable cannot be set over max 25%. TaxFee + liquidityFee + devFee must not be over 100%. In this case the transferAmount will be 0.

Pending

#3 medium Issue
Lock user funds with maxTxAmount
CoinToken.sol
L647-649
Description

The owner is able to set the maxTxAmount variable to 0. When this happen nobody is able to buy/sell any tokens anymore.

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
CoinToken.sol
L535
L763
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
CoinToken.sol
L635-637
L639-641
L643-645
L647-649
L903-905
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
CoinToken.sol
L472
L472
L651
Description

Check that the address is not zero.

Pending

#4 low Issue
State variable visibility
CoinToken.sol
L454
Description

Provide the visibility to the state variable

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
CoinToken.sol
L209-212
L215-219
L223-228
L231-236
L509-511
L513-515
L517-519
L521-523
L530-533
L535-537
L539-542
L544-548
L550-553
L555-558
L560-562
L564-566
L568-575
L577-586
L594-601
L627-629
L631-633
L647-649
L651-653
L656-659
L759-761
Description

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

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
CoinToken.sol
L175-188
L135-137
L139-141
L143-145
L147-152
L165-167
L169-173
L154-156
L158-162
L123-127
L129-133
L114-117
L91-96
L80-82
L98-103
L20-26
L47-52
L54-59
L35-45
L28-33
Description

Remove unused functions.