HydraMeshnet Info
The all-in-one radio meshnet solution for building blackout-resilient free market societies with secure digital cash payments in crisis regions and beyond.
Team and KYC Verification
The KYC verification for this project is currently in progress.
The team has submitted their information and verification is pending.
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.
Contract is upgradeable
The contract uses a proxy pattern or similar mechanism, enabling future upgrades. This can introduce risks if the upgrade mechanism is not securely managed.
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.
Ownership Privileges
- The DEFAULT_ADMIN_Role can create and mint new tokens to any address, for any declared "purpose," up to the TOTAL_SUPPLY limit.
- The DEFAULT_ADMIN_Role can destroy tokens from any user's wallet without their consent.
- The DEFAULT_ADMIN_Role can halt all major contract functions, including token transfers.
- The DEFAULT_ADMIN_Role can resume all contract functions after they have been paused.
- The DEFAULT_ADMIN_Role can grant or revoke the BRIDGE_ROLE to any address.
- The DEFAULT_ADMIN_Role can grant or revoke the DEFAULT_ADMIN_ROLE itself, effectively transferring complete control of the contract to another address.
- The BRIDGE_ROLE can mint new tokens when they are bridged from the native HMESH chain, up to the TOTAL_SUPPLY limit.
- The BRIDGE_ROLE can burn tokens from any user's wallet to facilitate bridging tokens back to the native HMESH chain. This is a critical privilege, as it allows the bridge to destroy tokens it does not own.
Note - This Audit report consists of a security analysis of the HydraMeshnet smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the HydraMeshnet 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
Findings and Audit result
medium Issues | 2 findings
Resolved
#1 medium Issue
Excessive Admin Privileges
The address holding the DEFAULT_ADMIN_ROLE has complete and unilateral control over the contract. It can pause all token transfers, mint new tokens at will, destroy tokens from any user's account, and reassign any role (including its own). This creates a single point of failure where a compromised admin key leads to a total loss of funds and trust.
Resolved
#2 medium Issue
Bridge Can Arbitrarily Burn User Tokens
The burnForBridge function allows any address with the BRIDGE_ROLE to burn tokens from any user's wallet by specifying their address in the from parameter. This is a critical vulnerability that allows a malicious or compromised bridge to steal funds directly from any token holder.
informational Issues | 1 findings
Acknowledged
#1 informational Issue
Floating pragma solidity version
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.