Owner privileges
Comments
Owner privileges
- mint
- pause/unpause
- snapshot
- removeSender
- addSender
- Senders can stake/release for other addresses without allowance
- freeze
- Blacklisted addresses cannot stake and transfer. Unstake is possible
Note - This Audit report consists of a security analysis of the DCC 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 DCC team, other contracts associated with the project were not audited by our team. 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
40
State variables
public
1
Total lines
of code
1735
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
Missing event
L1622
L1627
L1636
Emitting an event for the variable is recommended
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L1083-1094
L1101-1112
L133-135
L1166-1172
L1174-1176
L731-734
L938-970
L976-981
L885-921
L927-932
L989-1013
L1019-1024
L705-707
L712-714
L741-820
L825-831
L838-869
L874-879
L607-612
L617-622
L627-632
L677-682
L667-672
L647-652
L657-662
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L199-201
L207-209
L224-226
L250-254
L273-277
L295-300
L314-318
L334-343
L523-525
L538-541
L1284-1288
L1293-1297
L1431-1433
L1439-1442
L1622-1624
L1627-1632
L1634-1638
L1708-1710
L1712-1714
L1716-1718
L1720-1722
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.