WAU - We All United Info

Someone yesterday did not have money to celebrate his birthday, someone today cannot put food on the table for his kids, someone tonight will sleep rough and someone tomorrow will not be able to pay his bills. These are only a few of the millions of stories. Come to us, tell your story and we may be able to help. We are one… WE ALL UNITED. Looking for a good and trustworthy project? Scams, honeypots and rug pulls everywhere? Welcome to the most amazing, united, fun, friendly, engaging, respected and helping community ever... WE ALL UNITED!

WAU - We All United Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

85.26
Poor Excellent

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

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xbE2e...33a7
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/10/08
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 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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

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.

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.


  • SafeMath library is unnecessary because safemath functionality is implemented above floating pragma version 0.8.4 by default. We recommend you to remove the "SafeMath" library and use raw mathematical operations instead
  • addresses that are excluded by the owner cannot call the deliver function
  • The liquidty will be added to the owner. Be aware of it because the owner can drain out the liquidity pool.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
LiquidityGeneratorToken.sol
L1075
L1440
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
LiquidityGeneratorToken.sol
L1242-1248
L1250-1259
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Tautology or contradiction (tautology)
LiquidityGeneratorToken.sol
L972-1043
L972-1043
L972-1043
Description

Fix the incorrect comparison by changing the value type or the comparison.

Pending

#4 low Issue
State variable visibility is missing
LiquidityGeneratorToken.sol
L953
Description

The state variable visibility is missing: - "inSwapAndLiquify"

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
LiquidityGeneratorToken.sol
L494-496
L504-510
L523-529
L537-548
L583-585
L593-602
L556-558
L566-575
L441-451
L469-474
L610-630
L106-108
L376-385
L336-338
L402-411
L207-213
L249-254
L261-266
L232-242
L220-225
Description

Remove unused functions.