Dulion
In response to the growing worldwide population and its resulting gradual impact on the world economy, blockchain technology became available to transform the digital economy of the globe by way of the development of crypto money through a group of peers. Therefore, we made the decision to introduce a deflationary token with an anti-whale mechanism integrated as well as other criteria to combat rug pull, dumps, and whales with the intention of rewarding its investors.
Owner privileges
Comments
No Audit Comments.
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
74
State variables
public
24
Total lines
of code
1330
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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L842
L1072
Rename the local variables that shadow another component. Rename the local variables that shadow another component. In this case, âownerâ is shadowing the variable with the Ownable contractâs âownerâ variable
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L901
L910
L924
L928
L932
L949
L953
L960
L972
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L779
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L359-380
L319-321
L329-331
L344-346
L354-357
L266-275
L293-299
L238-241
L437-447
L410-419
L426-429
L421-424
L395-397
L399-401
L211-213
L227-230
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L737
L740
L743
L746
L749
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 Issue
Unused return values (unused-return)
L1233-1246
Ensure that all the return values of the function calls are used.
Pending
#4 Issue
Contract doesnât import npm packages from source (like OpenZeppelin etc.)
L6-695
We recommend importing all packages from npm directly without flatten the contract. Functions could be modified or can be susceptible to vulnerabilities
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.