Gasmeta Info

$PIPE coin is the native cryptocurrency of the PIPE Network, a blockchain platform. It is used for various purposes within the network, including staking, transaction fees, and governance.

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

39.89
Poor Excellent

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.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x7dE3...7a55
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/05/03
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 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 not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

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 mint new tokens up to a maximum total supply of 125 million tokens.
  • The owner can blacklist/un-blacklist any arbitrary wallet from transferring tokens.
  • The admin or operator wallet can update any arbitrary address as the admin and operator wallet address.
  • The admin or operator wallet can transfer stuck tokens from the contract to the user wallet including contract's own tokens.

Note - This Audit report consists of a security analysis of the Gasmeta 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 Gasmeta 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 | 1 findings

Pending

#1 medium Issue
The owner can blacklist wallets.
QuantumPipelineToken.sol
L1012-1015
Description

The owner can blacklist wallets from transferring tokens for an unlimited period of time which is not recommended as this can lock the user's funds indefinitely. There must be a locking period in the contract so that the user should not be locked for an unlimited period of time.

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
QuantumPipelineToken.sol
L777
L981
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Access Control (events-access)
QuantumPipelineToken.sol
L1264-1267
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
QuantumPipelineToken.sol
L1264
L1264
L1273
Description

Check that the address is not zero.

Pending

#4 low Issue
Remove safemath library.
QuantumPipelineToken.sol
L207-418
Description

The 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 | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
QuantumPipelineToken.sol
L77-79
L85-88
L736-738
L743-745
L750-752
L769-772
L777-779
L788-791
L805-817
L831-834
L850-857
L867-870
L880-883
L895-901
L1037-1040
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)
QuantumPipelineToken.sol
L645-657
L499-501
L509-515
L528-534
L542-551
L584-586
L594-601
L559-561
L569-576
L450-456
L474-479
L633-643
L609-625
L19-21
L326-328
L382-391
L342-344
L408-417
L312-314
L213-219
L255-260
L267-272
L238-248
L226-231
Description

Remove unused functions.