Crypto Balls Info
CryptoBalls is an NFT-driven memecoin which aims to provide some BALLS into the crypto space. Cryptoballs NFTs will be created on narrative-based events and will provide a never ending buzz and virality into the crypto space. We still appreciate the human creation therefore, this project is 100% AI PROOF. All our NFTs are handmade with fun and positive energy.
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.
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 cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract owner can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
Contract can 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:
- 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 update the uniswap pair and router address.
- The owner can update the buy and sell liquidity fees of not more than 20%.
- The owner can update the max wallet and max transaction amount.
- The owner can update the marketing fees to not more than 20%.
- The owner can update the marketing wallet address.
- The owner can update the minimum amount to take fees.
- The owner can update the automated market maker pair address.
- The owner can exclude wallets from fees.
- The owner can exclude wallets from the maximum transaction amount.
- The owner can withdraw ETH and claim the stuck tokens from the contract.
Note - This Audit report consists of a security analysis of the Crypto Balls 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 Crypto Balls team. Other contracts associated with the project were not audited by our team. We recommend investors to 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
Pending
#1 medium Issue
Owner can set fees upto 40%.
The owner can set buy and sell liquidity and marketing fees up to 40%, so the total costs will become 40% in the contract, which is not recommended. There are no fees in the contract that should be more than 25%. Add a 'require' check so that the total fees cannot exceed 25%.
Pending
#2 medium Issue
The owner can lock tokens.
The owner can update the pair and router address after the initial deployment of the token which is not recommended as this can lock the transfer functionality in the contract if the router and pair address is set to an arbitrary address.
Pending
#3 medium Issue
Missing 'require' check
The owner can update the marketing wallet address to any contract address, which is not recommended as this can cause a potential honeypot in the contract if the owner has set the address to the contract address that cannot receive ETH. Add a 'require' check so that the address cannot be set to a contract address.
low Issues | 2 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.
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 | 2 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Conformity to Solidity naming conventions (naming-convention)
Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).