HyperProAI
0xef7D14ae3CcD0E8dF4667c7F6f61a8115a74152A 0xef7D...74152A

Static analysis Dynamic analysis Symbolic Execution SWC check

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.

Contract address
0xef7D...74152A
Network Ethereum Mainnet
License MIT
Compiler v0.8.7 v0.8.7+commit.e28d00a7
Type N/A
Language Solidity
Request date 2023/02/22
Revision date 2023/04/08
Critical
Passed
High
Passed
Medium
Passed
Informational
Passed

Owner privileges

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

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.

Audit Scope

This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.

We will verify the following claims:
  • Correct implementation of Token standard
  • Deployer cannot mint any new tokens
  • Deployer cannot burn or lock user funds
  • Deployer cannot pause the contract
  • Overall checkup (Smart Contract Security)
The auditing process follows a routine series of steps:
  • Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
  • Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  • Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  • Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  • Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
  • Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
  • Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.

Functions
public

35

State variables
public

21

Total lines
of code

300

Capabilities
Hover on items

Audit Details

Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.

Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.

low Issues

Pending

#1 Issue

Missing Events Access Control (events-access)

presale.sol

L262-264

Description

Emit an event for critical parameter changes.

Pending

#2 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 Issue

Missing Zero Address Validation (missing-zero-check)

presale.sol

L262

Description

Check that the address is not zero.

Pending

#4 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

Pending

#1 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 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.

Disclaimer

SolidProof.io reports are not, nor should be considered, an “endorsement” or “disapproval” of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any “product” or “asset” created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...)

SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.

SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProof’s position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.