LUNCHero
LuncHero is here to be the Voice & Flag-bearer for our strong army For far too long, our community has been criticized, mocked & even ridiculized by the intelligentsia & right-thinking people from Finance, Governments, and even the Crypto sphere itself. But we will not take this lying down! We are rising up! We are the LunC army and we will not be silenced! We will not rest until our voices are heard!
Owner privileges
Comments
Ownership Privileges:
- Enable/Disable cooldown, swap, and fees
- Include/Exclude accounts from the blacklist
- Open trading but cannot close it. Thus, open trading function can only be called once
- Set/Update maximum buy, sell, and max wallet amount but not less than 0.1% of the total supply.
- Set swap tokens at amount value within a range of 0.001% to 0.5%
- Set/Update marketing, BBWallet, and liquidity wallet address
- Include/Exclude accounts from fees and maximum trasnsaction
- Set/Update buy and sell fees up to 30%
- Set/Update cooldown blocks within a range of 0 to 10
- Swap contract's balance for ETH
- Withdraw stuck tokens/ETH but not the native ones
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
76
State variables
public
17
Total lines
of code
1095
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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L697
L724
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L712-720,844-944,1066-1088
Emit an event for critical parameter changes.
Pending
#3 Issue
Dangerous usage of `tx.origin` (tx-origin)
L731-773
Do not use `tx.origin` for authorization.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L24-26
L381-390
L341-343
L407-416
L212-218
L254-259
L266-271
L237-247
L225-230
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L614
L616
L618
L620
L623
L625
L627
L629
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 Issue
Missing error message
L738
We recommend always displaying an error message inside a require statement
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L642
L643
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L86-88
L94-97
L672-674
L676-678
L680-682
L692-695
L697-699
L701-704
L706-710
L712-714
L716-718
L720-722
L844-855
L857-860
L862-865
L867-870
L872-876
L878-885
L887-894
L896-903
L905-912
L914-916
L918-920
L922-926
L928-934
L936-942
L944-947
L1066-1069
L1071-1074
L1076-1079
L1081-1086
L1088-1093
Use the `external` attribute for functions never called from the contract.
Diagrams
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.