Welfare AI Info

Welfare Al is a pioneering cryptocurrency project that combines the power of artificial intelligence (AI) with the Binance Smart Chain (BSC) to create a revolutionary ecosystem. This ecosystem aims to democratize the crypto world, providing cutting-edge Al technology, secure staking pools, community-driven governance, and a range of utilities designed to optimize the staking experience and maximize rewards.

Welfare AI 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.61
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

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x64F3...eAd1
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/08/28
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.


Ownership Privileges
  • The owner can enable trading only once.
  • The owner can air-drop tokens to multiple addresses at once.
  • The owner can enable/disable swapping.
  • The owner can enable/disable the rescue swap, which means the contract balance will be sent to the marketing wallet address.
  • The owner can exclude wallets from fees.
  • The owner can change the automated market pair address.
  • The owner can update any address as the marketing wallet address.
  • The owner can update any address as a dev wallet address.
  • The owner can update any address as a grant wallet address.
  • The owner can reset tax amount to 0.

Note - This Audit report consists of a security analysis of the Welfare AI 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 Welfare AI team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 1 findings

Resolved

#1 medium Issue
Transfer of tokens without enabling trade.
WFARE.sol
L1066-1146
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 addresses manually, 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 owner can authorize the wallets used for the presale. 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.

low Issues | 5 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
WFARE.sol
L926
L930
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Zero Address Validation (missing-zero-check)
WFARE.sol
L1046
L1051
L1056
Description

Check that the address is not zero.

Pending

#3 low Issue
Floating pragma solidity version
WFARE.sol
L3
Description

Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#4 low Issue
Missing events arithmetic
WFARE.sol
L997-1001
Description

Emit all critical parameter changes.

Pending

#5 low Issue
Remove Safemath library.
WFARE.sol
L454-595
Description

compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow, It is recommended to remove the unwanted code in order to avoid high gas fees.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
WFARE.sol
L205-207
L213-215
L230-232
L237-239
L256-259
L264-266
L275-278
L293-301
L315-318
L334-337
L614-616
L633-636
L1183-1188
Description

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

informational Issues | 3 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
WFARE.sol
L10-13
L398-406
L575-577
L591-594
L699-702
L690-694
L670-676
L658-665
L681-685
L705-708
L712-716
Description

Remove unused functions.

Pending

#2 informational Issue
Conformity to Solidity naming conventions (naming-convention)
WFARE.sol
L31
L32
L49
L722
L908
L910
L912
L860
Description

Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).

Pending

#3 informational Issue
Unused state variables (unused-state)
WFARE.sol
L653
Description

Remove unused state variables.