LFGROW Info
LFGrow is a complete defi ecosystem, which encompasses a meme coin centric earning platform that brings value to dedicated stakers of our native token. This allows them to profit from short term traders of the token, as well as from revenue generated by the groundbreaking products in our ecosystem.
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.
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.
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
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.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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 set the leave early fee to not more than 5% (500 basis points).
- The owner can change the early withdrawal fee recipient address.
- The owner can modify the lock time period for staking (up to 10^8 seconds).
- The owner can withdraw any native chain tokens (ETH/BNB) sent to the contract.
- The owner can recover any token other than the staking token from the contract.
Note - This Audit report consists of a security analysis of the LFGROW smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the LFGROW 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
low Issues | 3 findings
Pending
#1 low Issue
Missing events arithmetic
It is recommended to emit all the critical parameter changes.
Pending
#2 low Issue
Missing zero check for amount.
The function lacks proper input validation, such as checking that amount > 0 before proceeding with the transfer. It is recommended that to check that the amount is greater than zero.
Pending
#3 low Issue
Precision Rounding in Token Withdrawals
The LFGStaking contract's withdraw function may encounter minimal precision loss during token-to-MAXI conversions. Despite using a standard 10^18 precision factor, edge cases involving very small withdrawal amounts or dust balances can result in minor rounding discrepancies. While not critical, these could leave negligible amounts of tokens unrecoverable for some users. To mitigate this, Implement a minimum withdrawal threshold to prevent dust creation. Add a "sweep" function allowing users to withdraw their entire balance regardless of conversion precision. Consider tracking accumulated rounding errors and redistributing them during the final withdrawal. Document these limitations transparently for users to understand potential minimal losses during partial withdrawals.