WUSHU Info

wushueth.io

Welcome to the ultimate digital hangout where cleverness meets class - this is WUSHU. In our online tribe, we cultivate camaraderie while swapping tips on the dynamic world of the latest meme currency. Prepare yourself for a transformative wave that's about to shake up the meme culture universe like never before.

WUSHU Logo

Team and KYC Verification

The team has securely submitted their personal information to SolidProof.io for verification.

In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.

Show KYC Certificate

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.

On-Chain Insights

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x650b...a6DC
Network Ethereum - Mainnet
License N/A
Compiler N/A N/A
Type N/A
Language Solidity
Onboard date 2023/06/20
Revision date In progress

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

This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.

The auditing process follows a routine series of steps:
  1. Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
  2. Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  3. Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  4. Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  5. Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
  6. Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
  7. Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been intentionally or otherwise modified 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.

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
  • Enable trading, but cannot disable it
  • Burn Tokens from own wallet
  • Enable/Disable wallets from transferring the tokens before the trading is enabled.

Note - This Audit report consists of a security analysis of the WUSHU Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the WUSHU team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.

Files and details

Findings and Audit result

low Issues | 2 findings

Pending

#1 low Issue
Missing Arithmetic Events
Wushu.sol
L611-619
Description

Emit events for critical parameter changes

Pending

#2 low Issue
Missing Error Message
Wushu.sol
L620
Description

Make sure to display an error message if the condition inside the "require" statement fails

medium Issues | 1 findings

Pending

#1 medium Issue
Owner needs to Enable Trading
Wushu.sol
L619
Description

The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize the addresses and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be authorized by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be authorized.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
Wushu.sol
L92-94
L100-103
L294-296
L302-304
L319-321
L326-328
L333-335
L345-348
L353-355
L364-367
L382-396
L410-413
L429-437
L607-609
L611-613
L615-617
Description

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

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Wushu.sol
L33-35
L563-567
Description

Remove unused functions.