Zoe Token Info

Zoe Token stood on the precipice of the crypto space and watched as investors lost their funds and scam projects rug pulled, because of happenings was Zoe Token given birth and Zoe means life, and we are here to bring life back to the çrypto currency industry with our 3 point trilogy.

Zoe Token Logo

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.

71.22
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x0344...f726
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/01/27
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.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burn function within the contract.

Ownership is renounced

Contract cannot 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.


Ownership Privileges
  • The owner can exclude/include wallets in fees.
  • The owner can set buy and sell fees up to 100%.
  • The owner can update any arbitrary address to the wallet dev address.
  • The owner can enable/disable swapping.
  • The owner can set any arbitrary value in the minimum swap threshold amount.
  • The owner can blacklist/un-blacklist wallets from transferring tokens.
  • The owner can enable/disable blacklist settings in the contract.
  • The owner can enable/disable token transfer without fees.
  • The owner can update any arbitrary value in the max transaction and wallet amount, including zero.
  • The owner can manually swap tokens to the dev wallet address.
  • The owner can claim the stuck tokens at any arbitrary address.
  • The owner can update any arbitrary address as the router and pair address.

The ownership has been renounced

Note - This Audit report consists of a security analysis of the Zoe 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 Zoe Token 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 | 3 findings

Resolved

#1 medium Issue
The owner can set fees upto 100%.
zoetoken.sol
L519-525
Description

The owner can update the buy and sell fees up to 100%, which is not recommended as this can cause the loss of funds for the users if the value is st to 100%. There should not be any fees in the contract that can be more than 25%.

Resolved

#2 medium Issue
The owner can blacklist wallets.
zoetoken.sol
L556-569
Description

The owner can blacklist wallets from transferring tokens as this can lock the user from transferring of tokens which can lock their tokens. There must be a locking period so the amount of tokens cannot be locked indefinitely.

Resolved

#3 medium Issue
The owner can lock tokens.
zoetoken.sol
L621-628
L821-836
Description

The owner can set any arbitrary value in the max transaction and max wallet amount, which can lock the token transfer for an indefinite period of time. It is recommended that the max transaction and max wallet amount should be at least 0.1% of the total supply so that the tokens cannot be locked. Also, the owner can set any arbitrary address in the router address, which will lock the tokens. It is recommended that the router address should not be changed after the initial deployment of tokens.

low Issues | 5 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
zoetoken.sol
L484
L657
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
zoetoken.sol
L519-525
L547-549
L621-623
L626-628
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
zoetoken.sol
L528
L834
Description

Check that the address is not zero.

Pending

#4 low Issue
Floating pragma solidity version.
zoetoken.sol
L2
Description

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

Pending

#5 low Issue
Remove safemath library
zoetoken.sol
L16-49
Description

The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
zoetoken.sol
L368
L369
L374
L372
L373
L376
L375
L384
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
zoetoken.sol
L155-158
L161-165
L459-461
L463-465
L467-469
L471-473
L479-482
L484-486
L488-491
L493-497
L499-502
L504-507
L510-512
L515-517
L528-531
L541-544
L547-549
L589-591
L772-779
L821-825
L828-831
L834-836
Description

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

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
zoetoken.sol
L116-129
L76-78
L80-82
L84-86
L88-93
L106-108
L110-114
L95-97
L99-103
L64-68
L70-74
L56-59
L31-33
L42-47
L27-29
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
zoetoken.sol
L369
L376
L405
L407
Description

Remove unused state variables.