RLGL Info
Welcome to $RLGL, the thrilling evolution of gamified tokenomics inspired by the legendary Netflix series, "Squid Game," delving into themes of life, death, and risk. The distinctive features of our token is what distinguishes us from other tokens. We embrace life's unpredictability, acknowledging that a single choice can alter your destiny. As developers, we've diligently woven this concept into our tokenomics, and we're excited to reveal the fruit of our labor – our brainchild. Join us on this exciting journey!
Overall Score
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
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 exclude wallets from fees.
- The owner can update the development wallet address.
- The owner can set the swap threshold amount, which can not be less than 500 tokens.
- The owner can set liquidity fees of not more than 3%.
- The owner can set the development fees of not more than 3%.
- The owner can update the automated market maker address.
- The owner can withdraw the contract's ETH to any wallet.
- The owner can burn tokens from the holder's wallet randomly, which cannot be more than 3%.
This contract uses on-chain randomness to burn tokens from the holders randomly, which may be predictable by the owner.
Note - This Audit report consists of a security analysis of the RLGL 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 RLGL 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
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
optimization Issues | 2 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.
Pending
#2 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
Functions that are not used (dead-code)
Remove unused functions.
Pending
#3 informational Issue
Costly operations in a loop (costly-loop)
Use a local variable to hold the loop computation result.
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:
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.