DAOWhale
0xdd15f8E5b17f8C40aE786002258600540EE4Eb0E 0xdd15...E4Eb0E

Static analysis Dynamic analysis Symbolic Execution SWC check

THE WHALE TANK; THE FIRST CRYPTO SHARK TANK GOVERNED BY THE COMMUNITY

Contract address
0xdd15...E4Eb0E
Network Ethereum Mainnet
License None
Compiler v0.8.17 v0.8.17+commit.8df45f5f
Type ERC20
Language Solidity
Request date 2022/10/26
Revision date 2022/10/26
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

  • Owner can
    • take out contract balance with "withdrawStuckETH" function
    • airdrop tokens to addresses

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

59

State variables
public

34

Total lines
of code

1068

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)

DAOWhale.sol

L483

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

DAOWhale.sol

L618-628

L668-684

L686-702

Description

Emit an event for critical parameter changes.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

DAOWhale.sol

L14-17

Description

Remove unused functions.

Pending

#2 Issue

Use private function instead of calling state variable directly

DAOWhale.sol

L647

Description

We recommend you to use the private function "_excludeFromMaxTransaction" in the external function "excludeFromMaxTransaction" instead of setting the "_isExcludedMaxTransactionAmount" directly because in the private function is also the event emitted and it is checking the "lpPair".

optimization Issues

Pending

#1 Issue

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

DAOWhale.sol

L136-138

L140-142

L144-146

L162-170

L172-180

L182-190

L192-209

L211-222

L224-239

Description

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.