Pump Master Info
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!
Overall Score
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.
On-Chain Insights
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 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.
Scope of Work
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
- 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
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)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 2 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Function initializing state variables (function-init-state)
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.
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:
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.