HongKongDAO
0xB1A1D06d42A43a8FCfDC7FDcd744f7eF03e8ad1a 0xB1A1...e8ad1a

Static analysis Dynamic analysis Symbolic Execution SWC check

In the wab3 new Internet era, companies such as blockchain public chains, games, financial management, social networking, shopping malls, and information services, including community da tokens, are gradually becoming more and more legalized in the global industry. In such a period of great development prospects, the HK service platform platform has clear choices, accurate positioning, and serves all blockchain digital financial platform participants. The platform includes multiple sections, task areas, and forum areas. Advertising area, information area, news area, asset aggregation area, we will use professional technology and meticulous service to introduce huge traffic to the platform, and at the same time we will give most of the wealth created to all workers who have paid for the HK platform

Contract address
0xB1A1...e8ad1a
Network Binance Smart Chain
License MIT
Compiler v0.8.18 v0.8.18+commit.87f61d96
Type N/A
Language Solidity
Request date 2023/04/07
Revision date 2023/04/08
Critical
Passed
High
Passed
Medium
Passed
Optimization
Passed

Owner privileges

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 can set high fees Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
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

Comments/Ownership Privileges

  • Set the status of Airdrop, and Liquidity pool to true or false, true will result in an airdrop to an 'ad' address which is randomly generated
  • The contract has a check for 'excluded from fees' for wallets but no function to implement it.
  • The owner can set the buy and sell tax up to 49%. It is recommended to put it under 25%
  • The owner can set the marketing pool address
  • The owner can transfer any type of tokens from the contract to the marketing pool address including the native ones

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

8

State variables
public

0

Total lines
of code

250

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

56

Capabilities
Hover on items

Functions
public

0

State variables
public

0

Total lines
of code

27

Capabilities
Hover on items

Functions
public

6

State variables
public

0

Total lines
of code

75

Capabilities
Hover on items

Functions
public

0

State variables
public

0

Total lines
of code

132

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

63

Capabilities
Hover on items

Functions
public

8

State variables
public

4

Total lines
of code

111

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)

BEP20.sol

L66

L225

L66

L225

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

Token.sol

L52

Description

Check that the address is not zero.

Pending

#3 Issue

Uninitialized state variables (uninitialized-state)

Token.sol

L10

Description

Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.

Pending

#4 Issue

Contract doesn’t import npm packages from source (like OpenZeppelin etc.)

Token.sol

-

Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

Pending

#5 Issue

Floating Pragma

Token.sol

-

Description

The current pragma Solidity directive is “>=0.6.0 <0.9.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

Missing error messages

Token.sol

L58

L59

Description

It is recommended to display error messages when the state of the contract reverts. Make sure to add error messages in the "require" statements

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.