Project Dreams Info
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.
Overall Score
Real-Time Threat Detection
Real-time threat detection, powered by Cyvers.io, is currently not
activated
for this project.
This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks.
For more information, click here.
TrustNet DataPulse
Summary and Final Words
No crucial issues found
The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint
It is not possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Contract cannot be locked
Owner cannot lock any user funds.
Token cannot be burned
There is no burn function within the contract.
Ownership is not renounced
Contract can be manipulated by owner functions.
Scope of Work
Final Words
The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.
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
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Pending
#1 medium Issue
Access Control
Anyone can call MAPSet and MAPRemove functions. This means that everyone can set nd remove MAP of any account
low Issues | 5 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low 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 low 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
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Pending
#3 informational Issue
Uninitialized local variables (uninitialized-local)
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.
The auditing process consists of the following systematic steps:
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.