Andy AI Info

Welcome to ANDY MEMECOIN, where memes turn into money! Co-founded by meme aficionados Andy and Pepe, our platform revolutionizes the way memes are valued. Tired of seeing talented meme creators go unrewarded, we crafted a digital currency that rewards every share and creation.

Andy 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.

16.95
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.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x3cA5...E46f
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/05/13
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 burning within the contract without any allowances

Ownership is not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

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 distribute dividends.
  • The owner can set any arbitrary amount for the minimum token required for dividends.
  • The owner can exclude wallets from dividends.
  • The owner can enable/disable anti-sync.
  • The owner can launch tokens only once.
  • The owner can whitelist wallets from fees.
  • The owner can update any arbitrary address as the fund wallet address.
  • The owner can update the automated market maker pair address.
  • The owner can set any arbitrary amount in the claim wait.
  • The owner can update any arbitrary amount in the holder reward condition.
  • The owner can set any arbitrary amount in the minimum dividend amount.
  • The fund wallet address can transfer tokens and ETH from the contract to his wallet including contract's own tokens.

Note - This Audit report consists of a security analysis of the Andy 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 Andy 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 | 3 findings

Pending

#1 medium Issue
Transfer of tokens without enabling trade.
AndyAI.sol
L1152-1314
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 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.

Pending

#2 medium Issue
Liquidity is added to externally owned address.
AndyAI.sol
L1316-1335
Description

The contract's liquidity is automatically added to the 'generateLpReceiverAddr' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.

Pending

#3 medium Issue
Missing 'require' check.
AndyAI.sol
L1094-1096
Description

The owner can set any arbitrary amount to the fund address, including zero address, as this can lead to a loss of funds if the owner sets the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.

low Issues | 6 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
AndyAI.sol
L583
L584
L639
L643
L652
L661
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
AndyAI.sol
L1436-1438
L1487-1489
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
AndyAI.sol
L229
L1094
Description

Check that the address is not zero.

Pending

#4 low Issue
Floating pragma solidity version
AndyAI.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

#5 low Issue
Remove safemath library
AndyAI.sol
L5-85
L168-215
Description

The 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.

Pending

#6 low Issue
Missing Threshold
AndyAI.sol
L1436-1438
L1487-1489
L1491-1493
L1495-1497
Description

The owner can update any arbitrary value in the claim wait, minimum tokens required for dividends, and minimum tokens for dividends, which is not recommended as this can block the users' dividends if the claim wait is set to an excessive value. Also, there must be a limit for the minimum tokens required for dividends. If the amount is set to an excessive value, the user cannot claim any rewards.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
AndyAI.sol
L966
L968
L1118
L938
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
AndyAI.sol
L237-239
L246-249
L251-258
L317-319
L321-323
L343-351
L353-361
L363-371
L373-388
L390-401
L403-417
L590-601
L605-607
L639-641
L652-659
L812-864
L1057-1059
L1080-1083
L1085-1092
L1098-1104
Description

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

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
AndyAI.sol
L92-95
L675-690
L106-108
L110-119
L121-127
L129-131
L6-8
L10-21
L73-75
L77-84
L198-201
L180-184
L172-178
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
AndyAI.sol
L170
Description

Remove unused state variables.