RLGL
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!
Owner privileges
Comments
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.
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
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
/
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
medium Issues
Pending
#1 Issue
Liquidity is added to externally owned account.
L229-239
The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
low Issues
Pending
#1 Issue
Floating pragma solidity version.
L3
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
#2 Issue
Missing visibility.
L28
It is recommended to add 'public' or 'private' during the initialization of a state variable or a mapping.
Pending
#3 Issue
Missing zero or dead address check.
L53-78
Check that the address is not zero or dead.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L21-23
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L62-64
L70-72
L87-89
L94-97
L101-103
L113-117
L122-124
L136-140
L158-167
L181-185
L201-210
Use the `external` attribute for functions never called from the contract.
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.