Chimpz Info
CHIMPZ, including the project, token, website, smart contracts, and apps (“CHIMPZ”), is not a licensed or regulated financial service in any jurisdiction. Any terminology used in this document, on the website, or in the app is for reference only and does not hold any legal meaning. CHIMPZ is a fully decentralized, community-driven project with opensource, audited smart contracts. The CHIMPZ token is a utility token and is not a regulated security or stablecoin. This document is not a contract or investment offer. Users should seek legal and technical advice before using CHIMPZ, as there are inherent risks associated with blockchain and crypto systems, including potential losses.
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 not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
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 approve max tokens to dexRouter address.
- The owner can change the router address before the liquidity is added to the contract.
- The owner can change the liquidity pair address.
- The owner can initialize the token multiple times before the trading is enabled.
- The owner can exclude wallets from fees.
- The owner can exclude wallets from protection to move tokens before enabling the trade.
- The owner can update the status of Anti-Snipe
- Lock Taxes once and cannot enable them ever again
- Set Taxes and Tax Distribution Ratios
- Set swap amount that will impact the prize but not more than 1.5%
- Enable/Disable swap
- Exclude PResale contract addresses from limitations
- Withdraw native tokens from the contract balance before the liquidity has been added
- Include/Exclude wallets from reward
Note - This Audit report consists of a security analysis of the Chimpz 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 Chimpz team. Our team did not audit other contracts associated with the project. We recommend investors to do their research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 2 findings
Pending
#1 low Issue
Missing Events Arithmetic
Emit an event for critical parameter changes.
Pending
#2 low Issue
Missing Zero Address Validation
Check that the address is not zero.
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 | 3 findings
Pending
#1 informational Issue
Uninitialized local variables
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
Pending
#2 informational Issue
Unused return values
Ensure that all the return values of the function calls are used.
Pending
#3 informational Issue
Local variables used prior their declaration
Move all variable declarations prior to any usage of the variable, and ensure that reaching a variable declaration does not depend on some conditional if it is used unconditionally.