Facepalm Coin
0x51e037291865dcC6277A0999de5e5934616eD3aE 0x51e0...6eD3aE

Static analysis Dynamic analysis Symbolic Execution SWC check

The Facepalm Coin project was formed by visionaries who intend to propel cryptocurrency innovation to new heights. Passion and creativity are what drive the team to go beyond the limits of DeFi to establish a coin worthy of your wallet! We plan on taking over the crypto space in a short amount of time.

Contract address
0x51e0...6eD3aE
Network Ethereum Mainnet
License MIT
Compiler v0.8.4 v0.8.4+commit.c7e474f2
Type N/A
Language Solidity
Request date 2024/03/29
Revision date 2024/04/03
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

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

Ownership Privileges:

  • Included/Exclude wallets from reward and fees.
  • Set the number of tokens to sell in order to add liquidity but not less than 0.05% of the total supply.
  • Set the fees in the contract but not more than 25%.
  • Enable/Disable Pinksale's antibot.

Note - This Audit report consists of a security analysis of the Facepalm coin smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token and one rewards contract for the Facepalm coin team. Our team did not audit other contracts associated with the project. 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)
The auditing process follows a routine series of steps:
  • 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

69

State variables
public

11

Total lines
of code

1675

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)

AntiBotLiquidityGeneratorToken.sol

L1102

L1473

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

AntiBotLiquidityGeneratorToken.sol

L1265-1271

L1273-1282

L1284-1290

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

AntiBotLiquidityGeneratorToken.sol

L1003

Description

Check that the address is not zero.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

AntiBotLiquidityGeneratorToken.sol

L494-496

L504-510

L523-529

L537-548

L583-585

L593-602

L556-558

L566-575

L441-451

L469-474

L610-630

L106-108

L376-385

L336-338

L402-411

L207-213

L249-254

L261-266

L232-242

L220-225

Description

Remove unused functions.

Pending

#2 Issue

Unused return values (unused-return)

AntiBotLiquidityGeneratorToken.sol

L1569-1582

Description

Ensure that all the return values of the function calls are used.

optimization Issues

Pending

#1 Issue

Public function that could be declared external (external-function)

AntiBotLiquidityGeneratorToken.sol

L165-167

L173-176

L1072-1074

L1076-1078

L1080-1082

L1093-1100

L1102-1109

L1111-1118

L1120-1135

L1137-1148

L1150-1164

L1166-1168

L1170-1172

L1174-1184

L1186-1199

L1214-1222

L1261-1263

L1468-1470

Description

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.