Project Dreams
0x83e575d69397541Cf89f80758eeE63bdA8345Bf6 0x83e5...345Bf6

Static analysis Dynamic analysis Symbolic Execution SWC check

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.

Contract address
0x83e5...345Bf6
Network Binance Smart Chain
License MIT
Compiler v0.8.0 v0.8.0+commit.c7dfd78e
Type ERC20
Language Solidity
Request date 2023/01/02
Revision date 2023/01/08
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

No critical 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.
Comments

The owner can authorize/unauthorize multiple accounts/wallets/contract addresses to perform certain actions in the contract and these addresses can perform these actions even after the ownership is renounced.

Authorized Privileges:

  • Trigger buyback, clear buyback multiplier
  • Set auto buyback settings with any arbitrary values
  • Set buyback multiplier settings within the range
  • Set transaction limit but not to zero or less than zero
  • Exempt accounts from dividends and fees
  • Set fee receivers, distribution criteria, swap back settings, and target liquidity with arbitrary values

OnlyToken Privileges:

The token address will be set as the deployer address of the dividend contract and it can perform certain actions:

  • Distribution Criteria
  • Set Share
  • Deposit
  • Process accounts

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)
The auditing process follows a routine series of steps:
  • 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

65

State variables
public

21

Total lines
of code

786

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 Events Arithmetic (events-maths)

ProjectDreams.sol

L287-290

L687-694

L696-701

L713-716

L736-746

L753-756

L758-761

Description

Emit an event for critical parameter changes.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

ProjectDreams.sol

L169

L748

L748

Description

Check that the address is not zero.

Pending

#3 Issue

Floating Pragma

ProjectDreams.sol

-

Description

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.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

ProjectDreams.sol

L703-705

L85-90

L74-76

L92-97

L17-23

L44-49

L51-56

L32-42

L25-30

Description

Remove unused functions.

Pending

#2 Issue

Function initializing state variables (function-init-state)

ProjectDreams.sol

L418

L465

Description

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 state variables (unused-state)

ProjectDreams.sol

L407

L411

Description

Remove unused state variables.

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

ProjectDreams.sol

L249

L262

L407

L409

L411

L410

L417

Description

Add the `constant` attributes to state variables that never change.

Pending

#2 Issue

Public function that could be declared external (external-function)

ProjectDreams.sol

L141-143

L148-150

L169-173

L707-711

Description

Use the `external` attribute for functions never called from the contract.

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.