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 not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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
Staking.sol
- The owner can start the staking program, which initializes the reward period.
- The owner can stop the staking program prematurely and disable all future staking.
- The owner can prevent users from staking any new tokens.
- The owner can re-enable staking after it has been paused.
- The owner can change the percentage fees for staking and unstaking not more than 10%.
- The owner can update the minimum stake amount.
- The owner can change the total reward budget.
- The owner can add reward tokens to the contract.
- The owner can withdraw the fees from the contract.
- The owner can emergency withdraw the fees and the unused rewards from the contract.
Note - This Audit report consists of a security analysis of the Aurk 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 Aurk 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
Resolved
#1 medium Issue
Missing limits in minimum stake and reward budget.
The setMinimumStake and setTotalRewardBudget functions lack crucial input validation, creating a medium-severity centralization risk. Without enforced limits, an owner could set an impossibly high minimum stake, effectively blocking new users, or set an unrealistically large reward budget to advertise a deceptive APY. This unchecked administrative power could mislead users and disrupt the contract's core functionality.
Resolved
#2 medium Issue
The owner can drain staked tokens.
The emergencyWithdrawAll function allows the contract owner to unilaterally withdraw the entire token balance of the contract. This includes all user-staked funds, not just fees or rewards. This function serves as an unprotected backdoor, enabling the owner to steal every asset held within the contract at any time. It represents a direct and severe threat to all users, as their deposited funds can be drained instantly by a malicious owner, completely undermining the contract's security and trustworthiness.
low Issues | 1 findings
Pending
#1 low Issue
Missing events arithmetic
It is recommended to emit all the critical parameter changes.
informational Issues | 1 findings
Pending
#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.