Zeetox Info
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.
Overall Score
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
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 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.
Scope of Work
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.
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.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Pending
#1 medium Issue
Owner can blacklist wallets.
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 | 4 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#3 low Issue
Old compiler version
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 low Issue
Missing 'require' error message.
It is recommended to add the error message in the 'require' check when it is used inside the function.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
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)
Remove unused functions.
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:
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.