Zoe Token
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.
Owner privileges
Comments
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.
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)
- 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
96
State variables
public
12
Total lines
of code
881
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
Resolved
#1 Issue
The owner can set fees upto 100%.
L519-525
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 Issue
The owner can blacklist wallets.
L556-569
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 Issue
The owner can lock tokens.
L621-628
L821-836
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
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L484
L657
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L519-525
L547-549
L621-623
L626-628
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L528
L834
Check that the address is not zero.
Pending
#4 Issue
Floating pragma solidity version.
L2
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 Issue
Remove safemath library
L16-49
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.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
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
Remove unused functions.
Pending
#2 Issue
Unused state variables (unused-state)
L369
L376
L405
L407
Remove unused state variables.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L368
L369
L374
L372
L373
L376
L375
L384
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
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
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.