Primeformer Info

At Primeformer, our mission is to bring laughter and entertainment to the world of cryptocurrencies, All while paying homage to the iconic Transformers franchise. We've designed Primeformer to be a community-driven token that embodies the spirit of fun, creativity, and innovation.

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

43.21
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
0x452E...6F06
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/06/27
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 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 authorized address can claim the stuck tokens even after ownership is renounced.
  • The authorized address can claim the contract's own tokens.

Note - This Audit report consists of a security analysis of the Primeformer 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 Primeformer team, other contracts associated with the project were not audited by our team. We recommend investors to 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
Authorized address can claim native tokens.
PrimeCoin.sol
L787-793
Description

Authorized address have the ability to claim the native tokens, even after the renouncement of the ownership. Also, authorized address have the ability to claim the contract's own tokens, It is recommended to add the check to restrict the user not to claim the contract's balance of its own tokens.

low Issues | 3 findings

Pending

#1 low Issue
Missing Zero Address Validation (missing-zero-check)
PrimeCoin.sol
L782
L787
Description

Check that the address is not zero.

Pending

#2 low Issue
Remove Safemath Library
PrimeCoin.sol
L576-775
Description

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.

Pending

#3 low Issue
Ownable contract is implemented but not used
PrimeCoin.sol
L778
Description

It is recommended to remove unused code to avoid high gas fees.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
PrimeCoin.sol
L181-183
L189-191
L213-215
L220-222
L232-236
L255-259
L277-282
L296-300
L316-325
L541-543
L549-552
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)
PrimeCoin.sol
L122-124
L396-412
L653-655
L695-697
L747-752
L711-713
L769-774
L681-683
L667-669
L728-733
L582-588
L624-629
L636-641
L607-617
L595-600
Description

Remove unused functions.