Matt Pepe Info

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.

Matt Pepe 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.

74.63
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
0xb619...c1C3
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/09/18
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 can blacklist addresses

It is 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.

Token transfer can be locked

Owner can lock user funds with owner functions.

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

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 2 findings

Pending

#1 medium Issue
The owner can blacklist wallets.
MTP.sol
L525-527
Description

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 medium Issue
The owner can set fees to more than 100%.
MTP.sol
L529-535
Description

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 | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
MTP.sol
L468
L491
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
MTP.sol
L503-505
L529-531
L533-535
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Floating pragma solidity version
MTP.sol
L2
Description

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 low Issue
Remove Safemath library.
MTP.sol
L28-79
Description

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.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
MTP.sol
L378
L376
L377
L382
L380
L402
L401
Description

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

Pending

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

Use the `external` attribute for functions never called from the contract.

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
MTP.sol
L119-136
L102-104
L106-108
L110-112
L114-117
L83-92
L94-100
L10-13
L71-73
L75-78
Description

Remove unused functions.