Project Dreams
Project Dreams aims to educate and bring awareness to decentralized finance by using different platoforms. Project Dreams podcast will host several DeFi project developers, experienced DeFi traders and knowledgeable DeFi individuals to share their experinces within the Defi industry. We connect the community to emerging and existing Defi projects by giving project developers a platform to share the details about their projects. Project Dreams will be launching a token and documenting the whole experience to share with listeners on their podcast. Listeners will get to have a in-depth analysis of what it is like to start their own DeFi project.
Owner privileges
Comments
Ownership Privileges:
- The owner can update the dead wallet address to any arbitrary address and if the dead fee is more than 0 then the fees will be transferred to this "Dead Address" set by the owner
- Exclude wallets from dividends and fees
- Update fees, claim wait, set balance of an account,
- Process account for dividends
- Set minimum token balance for dividends
- Update Uniswap router address, marketing wallet address, AMM Pair address, gas for processing
- Set swapTokensAtAmount to any value
- Manually Swap tokens
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
138
State variables
public
28
Total lines
of code
1707
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
Access Control
L1178,1189
Anyone can call MAPSet and MAPRemove functions. This means that everyone can set nd remove MAP of any account
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L816
L816
L864
L871
L878
L888
L1308
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1492-1494
L1500-1507
L1509-1515
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L816
L1319-1320
L1355-1356
L1375
L1496
Check that the address is not zero.
Pending
#4 Issue
Floating Pragma
-
The current pragma Solidity directive is â^0.8.0". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.
Pending
#5 Issue
Contract doesnât import npm packages from source (like OpenZeppelin etc.)
-
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L210-219
L228-237
L262-268
L242-257
L9-11
L898-904
L126-128
L130-133
L184-187
L155-161
L143-150
Remove unused functions.
Pending
#2 Issue
Unused state variables (unused-state)
L138
Remove unused state variables.
Pending
#3 Issue
Uninitialized local variables (uninitialized-local)
L1595
L1595
L1595
L1561
L1557
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L33-35
L37-40
L300-302
L308-310
L325-327
L351-354
L359-361
L370-373
L388-396
L410-413
L429-432
L821-832
L836-838
L864-866
L878-880
L1009-1011
L1058-1075
L1102-1147
L1161-1163
L1347-1349
L1351-1358
L1367-1373
L1379-1382
L1400-1405
L1419-1421
L1423-1425
L1427-1429
L1435-1437
L1482-1490
L1492-1494
L1496-1498
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.