LUNCHero Info

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!

LUNCHero 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.

89.53
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x332B...8F72
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/10/19
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 can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

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:
  • 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

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 (shadowing-local)
LUNCHero.sol
L697
L724
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
LUNCHero.sol
L712-720,844-944,1066-1088
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Dangerous usage of `tx.origin` (tx-origin)
LUNCHero.sol
L731-773
Description

Do not use `tx.origin` for authorization.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
LUNCHero.sol
L642
L643
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
LUNCHero.sol
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
Description

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)
LUNCHero.sol
L24-26
L381-390
L341-343
L407-416
L212-218
L254-259
L266-271
L237-247
L225-230
Description

Remove unused functions.

Pending

#2 informational Issue
Function initializing state variables (function-init-state)
LUNCHero.sol
L614
L616
L618
L620
L623
L625
L627
L629
Description

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 informational Issue
Missing error message
LUNCHero.sol
L738
Description

We recommend always displaying an error message inside a require statement