Crypto Balls
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.
Owner privileges
Comments
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.
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
100
State variables
public
17
Total lines
of code
1672
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
Pending
#1 Issue
Owner can set fees upto 40%.
L1389-1406
L1423-1440
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 Issue
The owner can lock tokens.
L1351-1380
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 Issue
Missing 'require' check
L1442-1453
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
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L1276
L1277
L1279
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Zero Address Validation (missing-zero-check)
L1351
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L83-85
L112-118
L172-174
L182-191
L145-147
L155-164
L58-63
L324-326
L599-614
L789-802
L813-824
L804-811
L773-780
Remove unused functions.
Pending
#2 Issue
Conformity to Solidity naming conventions (naming-convention)
L849
L1085
L1087
L1118
L1190
L1351
L1390
L1391
L1408
L1414
L1424
L1425
L1443
L1444
L1455
L1210-1211
L1212
Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L381-383
L389-391
L406-408
L432-436
L455-459
L477-486
L500-504
L520-529
L738-740
L746-749
L1363-1380
L1464-1469
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.