Pump Master
0x761c72346eE0a8dDb2cA9bbA2a4f70b4e91540D4 0x761c...1540D4

Static analysis Dynamic analysis Symbolic Execution SWC check

The $PMASTER is here! With a $PMASTER army big enough, anything is possible! We want to gather all our friends and make something memorable together bringing you plenty of gains. Utilizing tech from the previous bull run, tech that has yet to be seen, and memes – the $PMASTER take over is starting now! The newest and most exciting memecoin! With a community-driven approach and a burning passion for memes, we believe PumpMaster is the next big thing in the meme market. Join us on this journey to revolutionize the world of memecoins and let’s go to the moon together!

Contract address
0x761c...1540D4
Network Binance Smart Chain
License MIT
Compiler v0.8.4 v0.8.4+commit.c7e474f2
Type N/A
Language Solidity
Request date 2023/04/27
Revision date 2023/04/27
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 can blacklist addresses It is 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.
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.
Comments

Ownership Privileges

  • Include/Exclude accounts from fees, max transaction, blacklist and max wallet limit
  • Enable/Disable AMM address, and buy tax
  • Update fee divisor but cannot set it to more than 20%
  • Set max transaction amount, and max wallet limit to any arbitrary amount including zero, and lock user funds
  • Enable trading but cannot disable it
  • Withdraw any type of tokens from the contract except the native ones

Note for Investors: We only Audited an ERC20 token contract for PUMP MASTER Team. However, If the project has other contracts (for example, a Presale contract, etc), and they were not provided to us in the audit scope then we cannot comment on its security and we are not responsible for it in any way. We recommend everyone to do their own research

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

102

State variables
public

11

Total lines
of code

942

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 specification 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)

PMASTER.sol

L609

L614

L619

L636

L642

L670

L682

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

PMASTER.sol

L869-871

L873-875

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

PMASTER.sol

L877

L922

Description

Check that the address is not zero.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

PMASTER.sol

L132-134

L140-142

L144-147

L123-129

L19-22

L189-202

L213-224

L204-211

L226-240

L180-187

L100-102

L104-107

Description

Remove unused functions.

Pending

#2 Issue

Function initializing state variables (function-init-state)

PMASTER.sol

L519

L523

L524

L525

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.

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

PMASTER.sol

L514

L512

L513

L505

Description

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

Pending

#2 Issue

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

PMASTER.sol

L273-275

L277-280

L588-590

L592-594

L596-598

L600-602

L608-612

L618-622

L624-633

L635-639

L641-650

L652-654

L844-846

L848-850

L852-854

L881-884

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.