Pump IT Info

pumpitbsc.com

Discover Pump It ($PUMPIT), a meme cryptocurrency on Binance Smart Chain (BSC). With a passionate community, high growth potential, and upcoming listings on multiple exchanges. Pump It ($PUMPIT) offers a buyback system for consistent growth and will receive support from major crypto influencers upon public launch. Invest now and get ready to pump it.

Overall Score
81.39
Poor Excellent
Pump IT Logo

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

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xd0C1...ca6F
Network
BNB Smart Chain - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/08/15
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 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 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 and include wallets in fees.
  • The owner can exclude wallets from the max holding wallets limit.
  • The owner can include wallets in the max holding wallets limit.
  • The owner can change the marketing wallet address.
  • The owner can update the marketing fees to not more than 5%.
  • The owner can update the max wallet holding limit of not less than 1 million tokens.
  • The owner can set any number in the swap threshold amount.
  • The owner can enable/disable swapping.
  • The contract's balance will automatically transfer to the marketing wallet address (0xA349374011d821186b8B61A6491C5D332cbC873E) whenever the swapping is done.

Note - This Audit report consists of a security analysis of the Pump IT 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 Pump IT 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

low Issues | 5 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
PUMPIT.sol
L521
L531
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing variable visibility
PUMPIT.sol
L440
L445
Description

It is recommended to add 'public' or 'private' visibility in all variables.

Pending

#3 low Issue
Remove virtual keyword
PUMPIT.sol
L512
L524
L534
L543
L556
L639
L651
L668
Description

Remove the 'virtual' keyword from the functions that are not overridden. It is not recommended to add a virtual keyword on the functions that are not going to be overridden anywhere.

Pending

#4 low Issue
Owner can set any number to swap threshold amount.
PUMPIT.sol
L624-630
Description

It is recommended to add a certain threshold where the amount of swap tokens amount will lie otherwise if the threshold amount is set so high then no swapping will be executed.

Pending

#5 low Issue
Missing event
PUMPIT.sol
L598-604
Description

Emit all critical parameter changes.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
PUMPIT.sol
L440
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
PUMPIT.sol
L66-69
L71-78
L510-518
L531-539
L541-552
L554-566
L637-645
L647-659
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)
PUMPIT.sol
L39-42
Description

Remove unused functions.