Liquidity Rush Info

Liquidity Rush is revolutionizing the DeFi space on the Ethereum Network with its $LIQR Token, a unique asset designed for sustainable liquidity ownership. This innovative platform offers a dynamic approach to tokenomics and staking, empowering users to influence the market through decentralized liquidity.

Liquidity Rush 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.

73.03
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
0x27c5...C21f
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/01/27
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
  • Include/Exclude wallets from dividends
  • Update Claim Wait time and reward wallet address
  • Update Marketing Wallet address, Max Wallet, and Max Transaction amount
  • Update buy/sell tax
  • Set/Update Staking address
  • Withdraw all types of tokens from the contract balance
  • Airdrop tokens to wallets

Note - This Audit report consists of a security analysis of the LiquidityRush Token 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 LiquidityRush team. Our team did not audit other contracts associated with the project. We recommend investors 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
LIQR.sol
L1370
L1378
L1387
L1398
L2239
L2240
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic
LIQR.sol
L2727-2737
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation
LIQR.sol
L1470
L2243
L2666
L2671
L2784
Description

Check that the address is not zero.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external
LIQR.sol
L938-940
L1329-1340
L1344-1346
L1370-1372
L1386-1390
L1620-1652
L1681-1725
L1835-1837
L1843-1845
L1886-1890
L1909-1913
L1931-1936
L1950-1954
L1970-1979
L2333-2337
L2339-2343
Description

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

informational Issues | 4 findings

Pending

#1 informational Issue
Functions that are not used
LIQR.sol
L630-632
L659-661
L711-713
L721-728
L686-688
L696-703
L605-610
L760-770
L872-874
L1483-1485
L1177-1185
L1125-1132
L1088-1097
L1112-1118
L1103-1106
L1138-1152
L1077-1079
L458-460
L510-515
L474-476
L532-537
L491-496
L345-351
L387-392
L399-404
L370-380
L358-363
L1255-1258
L1226-1232
L1214-1221
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
LIQR.sol
L1209
Description

Remove unused state variables.

Pending

#3 informational Issue
Unused return values (unused-return)
LIQR.sol
L2383-2385
L2551-2566
Description

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

Pending

#4 informational Issue
Uninitialized local variables (uninitialized-local)
LIQR.sol
L2246
Description

Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.