Zook Protocol Info
Welcome to ZOOK Protocol, the driving force behind a new era of decentralized trading, replete with speed, power, and unparalleled flexibility. Say farewell to the constraints of traditional exchanges and say hello to a new world of trading possibilities.
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.
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.
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 burning within the contract without any allowances
Ownership is renounced
The contract does not include owner functions that allow post-deployment modifications.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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 enable trading only once.
- The owner can remove limits from the contract.
- The owner can disable transfer delay in the contract.
- The owner can update the swap threshold between 0.001% to 0.5% of the total supply.
- The owner can update the max transaction amount of not less than 0.1% of the total supply.
- The owner can update the max wallet amount of not less than 0.5% of the total supply.
- The owner can exclude wallets from the maximum transaction amount.
- The owner can enable/disable swapping.
- The owner can update the buy and sell fees of not more than 5%.
- The owner can exclude wallets from fees.
- The owner can update the automated market pair address.
- The owner can update the development, marketing, and liquidity wallet address.
- The owner can blacklist the wallets from transferring tokens.
- The liquidity of the contract is transferred to the liquidity wallet address.
The ownership of the token is renounced, which means the owner cannot set the parameters which are mentioned above in this report. Also, The liquidity of the token is locked. So, the liquidity wallet address cannot drain the locked liquidity from the contract. Also, when the liquidity is unlocked, then the liquidity will be accessible to the liquidity wallet address.
Note - This Audit report consists of a security analysis of the Zook Protocol 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 Zook Protocol 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
Resolved
#1 medium Issue
Liquidity is added to externally owned account.
The contract's liquidity is automatically added to the 'liquidityWallet' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
low Issues | 6 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
Dangerous usage of `tx.origin` (tx-origin)
Do not use `tx.origin` for authorization.
Pending
#5 low Issue
Floating pragma solidity version.
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
#6 low Issue
Remove safemath library.
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)
Add the `constant` attributes to state variables that never change.
Pending
#2 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.