HyperProAI Info

The HyperproAI Platform Combines Blockchain And AI To Produce A New AI Fabric That Offers Superior Current-Day Usable AI Functionality While Progressing Toward The Realization Of The Team Visions Of Artificial General Intelligence. The Hyperpro Team Develops Smart Contract Which Aids Creation Of Successful Applications Cutting Across Various Quarter Of The WEB3 Ecosystem. HyperproAI Maximizes Participation From Various AI Players In The Ecosystem Worldwide, Including Developers, Universities, Computing Power Providers, SMEs, Financial Institutes, Data Providers, Etc. By Using The HPO Token As The Platform's Universal Currency.Set Up Automated Trading Strategies Based On Key Metrics And Order Types.

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

37.71
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
0xef7D...152A
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/04/08
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
  • Change selling token, and USDT token address
  • Enable/Disable presale, and the tokens will only be available to claim once the owner manually disables the presale
  • Set supply per phase to any arbitrary value including zero
  • Change/Set the price of the selling token to any arbitrary value including near zero or to a really high value. However, it can be done mid-presale which is not recommended because the owner can let some users buy tokens for cheap, while some users will get the tokens for a greater price. Basically, it is price manipulation.
  • Change bonus percent to any arbitrary value including 100% and zero
  • Change/Set referral percentage to any arbitrary value including 100% or more, which will result in a scenario where the buyer and referrer will get an equal amount of tokens for the same price
  • Transfer any type of tokens from the presale contract
  • Set minimum tokens to purchase
  • The Owner can manually set the balance of addresses with any arbitrary amount of HPO tokens and then those wallets can claim their tokens.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Missing Events Access Control (events-access)
presale.sol
L262-264
Description

Emit an event for critical parameter changes.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
presale.sol
L213-219
L239-241
L243-249
L252-254
L257-259
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
presale.sol
L262
Description

Check that the address is not zero.

Pending

#4 low Issue
Missing Length check
presale.sol
L290
Description

Check that the length of both the arrays passes in the parameters is same before iteration, otherwise it may lead to calculation errors if the number of wallets didn't match the number of amounts.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
presale.sol
L84-85
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
presale.sol
L129-155
L158-187
L204-210
L243-249
L286-293
L295-299
Description

Use the `external` attribute for functions never called from the contract.