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.
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.
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
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
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
Findings and Audit result
low Issues | 5 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#3 low Issue
Floating pragma solidity version
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
Emit all critical parameter changes.
Pending
#5 low Issue
Remove Safemath library.
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.
medium Issues | 1 findings
Resolved
#1 medium Issue
Transfer of tokens without enabling trade.
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.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
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)
Remove unused functions.
Pending
#2 informational Issue
Conformity to Solidity naming conventions (naming-convention)
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)
Remove unused state variables.
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.
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.