Zeetox
0x21a00838E6b2D4aa3ac4BbC11111Be011E1ca111 0x21a0...1ca111

Static analysis Dynamic analysis Symbolic Execution SWC check

ZEETOX envisions the huge potential in medical cannabis and the disruption it brings to the HealthFi industry. On June 9 2022, Thailand became the first country in Asia to legalize cannabis nationwide. Short after, the ZEETOX team has acquired a piece of 113,600 sqm farmland in Chiang Rai, Thailand to cultivate cannabis. Using cannabis as one of the backbones of the project, ZEETOX aims to create a revolutionary movement to build a future global community with zero toxics.

Contract address
0x21a0...1ca111
Network Polygon
License None
Compiler v0.6.12 v0.6.12+commit.27d51765
Type N/A
Language Solidity
Request date 2023/12/07
Revision date 2023/12/07
Critical
Passed
High
Passed
Medium
1 Issue
Low
4 Issues
Informational
1 Issue
Optimization
1 Issue

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 can blacklist addresses It is 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

Ownership Privileges

  • The owner can lock and unlock the ownership privileges in the contract for 7 days. This means if the owner locked the contract, then the ownership is renounced for 7 days, and the owner of the contract will be able to unlock it after 7 days.
  • The owner can change the name and symbol of the token.
  • The owner can blacklist wallets from transferring tokens.
  • The owner can claim tokens and ETH to the different wallets from the contract.

Note - This Audit report consists of a security analysis of the Zeetox token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Zeetox team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.

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

26

State variables
public

5

Total lines
of code

573

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 blacklist wallets.

Token.sol

L559-562

Description

The owner can blacklist wallets from transferring tokens for an unlimited period of time which is not recommended. There must be a locking period so that the wallets cannot be blacklisted for an unlimited period.

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

Token.sol

L510

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

Token.sol

L565

Description

Check that the address is not zero.

Pending

#3 Issue

Old compiler version

Token.sol

L6

Description

Adding the constant latest version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#4 Issue

Missing 'require' error message.

Token.sol

L522-524

L538-541

L550-551

Description

It is recommended to add the error message in the 'require' check when it is used inside the function.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

Token.sol

L362-383

L322-324

L332-334

L347-349

L357-360

L269-278

L296-302

L241-244

L178-180

L194-200

L214-216

L230-233

L152-164

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

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

Token.sol

L417-419

L436-439

L445-449

L451-453

L456-461

L464-469

L503-505

L507-509

L510-512

L521-529

L531-535

L537-547

L549-557

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.