CADINU Bonus
CADINUâs Decentralized Exchange offers a myriad of crypto opportunities. Engage in functionalities like Voting, Staking, Farming, MultiSwap, and get thrilled by our Lottery and Click-to-Win features. Explore a comprehensive crypto universe designed for you.
Owner privileges
Comments
Ownership has been renounced in the following TX: https://bscscan.com/tx/0xc497f4a104de3bb4e409b92c04e87307ed1d787cf5c45141300b45fafdac3ae6
Owner privileges
- withdrawETH
- withdrawWrongToken
- transferOwnership
- renounceOwnership
Note - This Audit report consists of a security analysis of the CADINU Bonus 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 CADINU Bonus team. Our team did not audit other contracts associated with the project. We recommend investors do their 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
32
State variables
public
5
Total lines
of code
1139
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
Owner can withdraw native tokens
L1133
The owner is able to withdraw their own tokens from the contract. It is recommended to prevent passing the own contract address to the "withdrawWrongToken".
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L645
L835
Rename the local variables that shadow another component.
Pending
#2 Issue
Floating pragma
L3
The contract is using a floating pragma. It is recommended to use a specific pragma version. Remove the "^" sign here.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L503-519
L499-501
L292-297
L309-315
L328-334
L346-365
L407-412
L420-433
L373-378
L386-399
L263-272
L467-472
L484-494
L441-459
L810-820
L852-862
L21-23
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L95-97
L103-108
L607-609
L614-616
L633-639
L644-649
L658-664
L678-693
L707-717
L733-746
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.