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.
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.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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.
Bridge privileges
The bridge address is an EOA. It can call the following functions:
- buyTokensBySecondaryCurrency
- buyTokensBySecondaryUSDT
Owner privileges
-
The owner can only set these parameters when the ICO is active:
- Set hard cap and soft cap
- Set maximum and minimum purchase value to any arbitrary number
- The owner can withdraw the contract balance only when the soft cap is reached, but it is not strict because the owner also controls the soft cap
- The owner can retake the remaining tokens from the contract when the ico is not active
- The owner can start and stop the ICO at any time but once stopped, a new ICO needs to be created which means the same ICO cannot be resumed once it is stopped.
- Set the withdrawal wallet
- The ownership of the contracts can never be renounced because of the custom-made ownable contract.
- The bridge address in the ICOPrimary contract must not be set as an EOA controlled by the deployer or owner because if done so then the owner can trigger secondary refunds to any arbitrary accounts manually.
- Be aware of this
Note for Investors: We only Audited a simple token contract and a Presale contract for Iniverse. However, If the project has other contracts (for example, a Staking contract etc), and they were not provided to us in the audit scope, then we cannot comment on its security, and we are not responsible for it in any way.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 1 findings
Pending
#1 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.