Runwago Info
Runwago is a next-generation Run-to-earn app designed for active runners who want to monetize their physical activity while staying motivated to achieve their healthy lifestyle goals. Its revenue model is 100% sustainable: rewards are funded by users who fail to meet their running goals, forfeiting their deposits into the Runwago Deposit Pool.
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.
Security Assessments
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 set the token generation event timestamp.
- The Default_ADMIN_ROLE can update the merkle root.
- The Default_ADMIN_ROLE can withdraw tokens from the contract.
Note - This Audit report consists of a security analysis of the Airdrop smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the Runwago 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
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 2 findings
Pending
#1 medium Issue
Unrestricted Admin Withdrawal Power
The Airdrop contract contains an emergencyWithdraw function that is exclusively accessible to the address holding the DEFAULT_ADMIN_ROLE. This function allows the administrator to unilaterally withdraw any amount of the runwagoToken held by the contract, up to its entire balance. If this power were to be used maliciously or if the admin's private key were compromised, it could lead to the complete draining of all tokens intended for the airdrop. This action would subsequently cause all legitimate user claims to fail, effectively blocking all participants from receiving their allocated tokens and leading to a total loss of user funds held within the contract.
Resolved
#2 medium Issue
Indefinite Claiming Lock via TGE Timestamp Control
The Airdrop contract grants the DEFAULT_ADMIN_ROLE exclusive control over setting the Token Generation Event (TGE) timestamp via the setTgeTimestamp function. This creates a critical centralization vulnerability. An administrator can indefinitely prevent the start of the token claiming period by either refusing to set the timestamp or by setting it to a distant future date. Since the claimTokens function is gated by a modifier that checks this timestamp, this gives the admin the unilateral power to permanently lock all user funds within the contract, preventing any airdrop participant from ever claiming their tokens.
low Issues | 1 findings
Resolved
#1 low Issue
Missing events arithmetic.
It is recommended to emit all the critical parameter changes.