OptimusZ7 Info

The OptimusZ7 Platform is a unified infrastructure platform based on the technical, traffic and ecological resources, and will be gradually open to the blockchain industry. It will make the construction of decentralized applications more efficient and cost-effective, and provide comprehensive empowerment in aspects of promotion, traffic, and resources. The OptimusZ7 Platform is an EVM compatible blockchain who solves the biggest problem of Dapp industry. The OptimusZ7 Platform will provide global developers with series of diverse innovative facilities and services.

OptimusZ7 Logo

Team and KYC Verification

The team has securely submitted their personal information to SolidProof.io for verification.

In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.

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.

36.53
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

Select the audit
"Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review"
Contract address
0xdBdf...1d12
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/02/27
Revision date 2025/02/27

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.

Token transfer can be locked

Owner can lock user funds with owner functions.

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.

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:

  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 start the presale.
  • The owner can update the active phases.
  • The owner can close the presale.
  • The owner can start the claim.
  • The owner can disable presale and start the claiming period.
  • The owner can claim tokens from the contract.
  • The owner can withdraw BNB from the contract.
  • The owner can update the token and USDC contract address.
  • The owner can update the presale price.
  • The owner can add/remove the tokens from the contract.
  • The owner can update the sale limit in the contract.
  • The owner can withdraw the unsold tokens from the contract.
  • The owner can update the presale dates in the contract.

Note - This Audit report consists of a security analysis of the OptimusZ7 presale smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the OptimusZ7 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 | 6 findings

Resolved

#1 medium Issue
Missing allowance check.
TokenPresale.sol
L386-419
Description

The function does not explicitly check whether the buyer has granted sufficient allowance before calling USDC.transferFrom, relying instead on the token’s own implementation to revert on insufficient allowance. This reliance can be problematic if the token deviates from the ERC20 standard, potentially resulting in unclear errors or even unintended behavior. To mitigate this risk, it’s advisable to either add an explicit check using USDC.allowance(msg.sender, address(this)) to ensure the allowance is adequate before proceeding, or to incorporate a library like OpenZeppelin’s SafeERC20, which standardizes token transfer behaviors and provides clearer error handling.

Acknowledged

#2 medium Issue
Aggregation of Multiple Purchases in buyTokensUSDC
TokenPresale.sol
L386-419
Description

The buyTokensUSDC function aggregates a user’s multiple purchases in the same phase into a single record, resulting in a loss of granular transaction details. Subsequent purchases overwrite the purchase timestamp and sum token and USDC amounts, hindering transparency, auditing, and dispute resolution. Moreover, vesting calculations may suffer inaccuracies from relying on aggregated data. This design makes it difficult to track individual events. To mitigate these issues, the contract should store each purchase as a distinct entry—using an array of records per user per phase—preserving unique timestamps and amounts for every transaction, thereby enhancing auditing precision and enabling accurate vesting computations.

Resolved

#3 medium Issue
Missing 'isContract' check.
TokenPresale.sol
L530-536
L538-544
Description

The contract lacks a validation check to ensure that specific parameters are contract addresses. Without this check, there is a risk that non-contract addresses (such as externally owned accounts, or EOAs) could be mistakenly set for parameters intended to reference other contracts. This could lead to failures in executing critical interactions within the contract, as EOAs do not support contract-specific functions. Implement a validation check to ensure that parameters designated as contract addresses are verified as such. This can be done using Solidity’s Address library function isContract, which checks if an address has associated contract code.

Acknowledged

#4 medium Issue
Owner’s Ability to Change Presale Dates Mid-Sale
TokenPresale.sol
L616-624
Description

The updatePresaleDates function allows the contract owner to modify the presale start and end dates while the presale is active. This means that even in the middle of a sale, the owner can adjust the sale period by providing new start and end timestamps. While this offers flexibility to respond to changing conditions, it also introduces a centralization risk: participants may be impacted by unexpected changes to the sale schedule. Mitigating this risk involves transparent communication with participants and possibly implementing additional governance mechanisms or time locks to restrict arbitrary changes.

Acknowledged

#5 medium Issue
Owner’s Ability to Withdraw Tokens mid sale.
TokenPresale.sol
L566-570
Description

This function grants the owner the authority to transfer any ERC20 tokens held by the contract to themselves. It accepts a token address as a parameter, checks the contract’s balance for that token, and if there’s any balance, transfers all of it to the owner. This means the owner could potentially withdraw tokens that were meant for presale participants, including presale tokens, posing a centralization risk. To mitigate this, mechanisms such as restricting withdrawal permissions for presale tokens, implementing time locks, or introducing governance oversight could be considered to ensure fairness and maintain participant trust.

Acknowledged

#6 medium Issue
Arbitrary Price and Sale Limit Adjustments
TokenPresale.sol
L546-560
L572-606
Description

Arbitrary price and sale limit adjustments represent a centralization risk where the owner can unilaterally modify critical sale parameters. In this contract, functions such as setTokenPrice and setTokensaleLimits allow the owner to change the token price and the total tokens allocated for a sale phase at any time. This means the owner could potentially lower the token price to benefit from increased sales or increase the token allocation to manipulate supply, thereby disadvantaging participants. Such flexibility undermines fairness, as buyers might purchase tokens under one set of conditions only for those conditions to be altered later without their consent, potentially leading to market manipulation and loss of investor trust. To mitigate this risk, implementing decentralized governance or multisignature approval for such adjustments is advisable. Time-locks or predetermined, immutable parameters could also be employed, ensuring any changes are transparent and subject to community oversight, thereby protecting participant interests.

low Issues | 2 findings

Resolved

#1 low Issue
Floating pragma solidity version
TokenPresale.sol
L6
Description

Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#2 low Issue
Missing events arithmetic
TokenPresale.sol
L348-384
L530-544
L616-624
Description

Emit all the critical parameter changes.

informational Issues | 1 findings

Resolved

#1 informational Issue
Function that are not used (Dead code).
TokenPresale.sol
L49
L63
Description

Remove unused code.