PandaPump Info
PandaPump is a meme coin project built with purpose that blends fun with functionality across a dynamic crypto ecosystem. Built on the Base network, our mission is to foster a vibrant, engaged community centered around $PPUMP. Our ecosystem includes: • A meme token ($PPUMP) at the heart of our brand • A participation platform designed to provide long term engagement • A dual utility based NFT collection To ensure the safety and transparency of our ecosystem, we’ve partnered with SolidProof to audit our smart contracts. This audit reflects our commitment to responsible development and community trust. PandaPump is where creativity meets transparency and trust — and we’re just getting started.
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.
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.
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 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 burning within the contract without any allowances
Ownership is renounced
The contract does not include owner functions that allow post-deployment modifications.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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 contract includes functions that, prior to renouncement, allowed the owner to:
- Update the treasury address
- Exclude wallets from fees
- Toggle swapping
- Adjust liquidity thresholds
- Set buy/sell fees up to 25%
However, ownership has been renounced. These functions are now permanently disabled, and no changes can be made to the contract’s settings.
Note - This Audit report consists of a security analysis of the PandaPump Token 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 PandaPump 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
Findings and Audit result
medium Issues | 3 findings
Resolved
#1 medium Issue
The contract can lock ETH
The CoinToken contract swaps tokens for ETH but lacks a function to withdraw accumulated ETH, potentially locking funds. While addLiquidityETH reinvests some ETH into liquidity, it does not use all ETH, leaving excess ETH trapped in the contract. The swapTokensForEth function sends ETH to address(this), but without a withdrawETH() function, it cannot be retrieved. To fix this, ETH should either be sent directly to the treasury or a withdrawal function should be implemented. Without this fix, any surplus ETH from swaps remains inaccessible, leading to locked funds and inefficient liquidity management.
Resolved
#2 medium Issue
Liquidity is added to externally owned address.
The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
Resolved
#3 medium Issue
Missing Threshold
The function setNumTokensSellToAddToLiquidity allows the owner to set the token amount required for liquidity swaps but lacks a maximum threshold to prevent excessive values. Without a limit, the owner could set an extremely high value, blocking liquidity additions indefinitely because the required token balance may never be reached. This can disrupt the token’s auto-liquidity mechanism, reducing market stability. To fix this, a reasonable upper limit should be enforced, ensuring liquidity functions properly while preventing accidental or malicious misconfigurations that could hinder token liquidity management and trading efficiency.
low Issues | 2 findings
Acknowledged
#1 low Issue
Old compiler version
Adding the latest constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Resolved
#2 low Issue
Missing events arithmetic
Emit all the critial parameter changes.