Matt Pepe
Matt Pepe, the ultimate meme coin, stands proud as a heartfelt tribute to the real father of Pepe, Matt Furie. As the visionary creator of the iconic Pepe the Frog, Matt Furie laid the foundation for a global phenomenon that gave birth to countless internet memes, representing humor, freedom of expression, and unity among diverse communities.
Owner privileges
Comments
Ownership Privileges
- The owner can exclude wallets from fees.
- The owner can set any arbitrary value on the minimum swap amount before swap.
- The owner can blacklist wallets for an unlimited period of time.
- The owner can set any arbitrary value into buy and sell tax.
- The contract balance will be transfer to the marketing wallet(0x002170ae4186aC7402d27F2E3f8a86E6E503E252) after swapping of tokens.
Note - This Audit report consists of a security analysis of the Matt Pepe 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 Matt Pepe 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
86
State variables
public
11
Total lines
of code
627
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
The owner can blacklist wallets.
L525-527
The owner can blacklist wallets for an unlimited period of time and then that user will not be able to transfer their tokens to any other wallets which is not recommended.
Pending
#2 Issue
The owner can set fees to more than 100%.
L529-535
The owner can set buy and sell tax to 100% or more than 100% through this owner can lock the funds and users will not be able to transfer their tokens which is not recommended. No fees should be more than 25% of the contract.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L468
L491
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L503-505
L529-531
L533-535
Emit an event for critical parameter changes.
Pending
#3 Issue
Floating pragma solidity version
L2
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
#4 Issue
Remove Safemath library.
L28-79
compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow, It is recommended to remove the unwanted code in order to avoid high gas fees.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L119-136
L102-104
L106-108
L110-112
L114-117
L83-92
L94-100
L10-13
L71-73
L75-78
Remove unused functions.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L378
L376
L377
L382
L380
L402
L401
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L159-162
L164-168
L448-450
L452-454
L456-458
L460-462
L468-470
L472-475
L477-480
L482-484
L486-489
L499-501
L507-509
L514-517
L519-523
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.