Raflex Info

WELCOME TO THE FIRST BLOCKCHAIN-INSPIRED MARKETPLACE, FREELANCING, E-LEARNING PLATFORM AND MORE! Your one-stop-shop platform for todays and future innovations! Bringing traditional businesses to the digital and decentralized world for individuals and corporate organizations from diverse backgrounds, languages, races, ages, professions, and interests.

Overall Score
79.04
Poor Excellent
Raflex Logo

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

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x7c28...aE20
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/02/04
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:
  • Included/Exclude wallets from reward and fees
  • Set the number of tokens to sell in order to add liquidity but not less than 0.05% of the total supply
  • Set the fees in the contract but not more than 25%
  • Enable/Disable pinksale's antibot

 

We recommend investors/users to 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

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
AntiBotLiquidityGeneratorToken.sol
L1102
L1473
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
AntiBotLiquidityGeneratorToken.sol
L1265-1271
L1273-1282
L1284-1290
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
AntiBotLiquidityGeneratorToken.sol
L1003
Description

Check that the address is not zero.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
AntiBotLiquidityGeneratorToken.sol
L165-167
L173-176
L1072-1074
L1076-1078
L1080-1082
L1093-1100
L1102-1109
L1111-1118
L1120-1135
L1137-1148
L1150-1164
L1166-1168
L1170-1172
L1174-1184
L1186-1199
L1214-1222
L1261-1263
L1468-1470
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)
AntiBotLiquidityGeneratorToken.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.

Pending

#2 informational Issue
Unused return values (unused-return)
AntiBotLiquidityGeneratorToken.sol
L1569-1582
Description

Ensure that all the return values of the function calls are used.