Hyper Pi Network Inu Info
Hyper Pi Network Inu is a meme token that only rewards investors for holding, the number of rewards received will increase over time if investors hold them longer. We are the safest place for long and short-term investors in the meme category.
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.
- Some of the functions has a modifier "onlyDev" which allows multiple authorities to do certain actions in the contract and we have also noticed that the fee of the swap is also being transferred to the "_developmentAddress" as well.
- The individual that controls the “_developmentAddress” can also transfer funds of this contract to another one of their choice. For more please read the Audit Results section.
- There can be multiple authorities in the contract that can make crucial changes to the contract rather than just the owner. According to the code, the owner can authorize any other arbitrary wallet address to perform the actions or call the functions with the "onlyDev" modifier. Therefore, one more situation arises from this scenario where the changes in the contract can be done even after the ownership has been renounced.
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
Own contract tokens are transferrable
The owner of the development address and the owner's address can transfer the whole balance of the contract to any address because there is no prevention against it. We recommend preventing passing your own contract address in the function.
low Issues | 5 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component. In this case, ”owner” is shadowing the variable with the Ownable contract’s “owner” variable
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#3 low Issue
Missing events
Emit an event for critical parameter changes.
Pending
#4 low Issue
Floating pragma is set
The current pragma Solidity directive is “^0.8.10". Contracts should be deployed with the same compiler version and flags that they have been tested with thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.
Pending
#5 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
informational Issues | 1 findings
Pending
#1 informational Issue
Unused state variables (unused-state)
Remove unused state variables.