Yieldz Info
yields.cc is a customized user interface that interacts with open-source smart contracts on several blockchains (e.g., Sonic, Ethereum, and others). The underlying open source smart contracts enable projects with tokens based on the ERC20 token standard, to create a single sided staking solution. With this staking solution, the project can reward uncertain incentives for the project's token holders.
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
Contract can be manipulated by owner functions.
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
StakingFactory.sol
- There are no ownership privileges in the contract.
Note - This Audit report consists of a security analysis of the Yieldz 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 Yieldz 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 | 1 findings
Resolved
#1 medium Issue
Missing Non-reentrant check.
The createStaking function in StakingFactory is vulnerable to reentrancy attacks due to the external call Address.sendValue(payable(_params.deployer), msg.value), which transfers Ether before the function completes. A malicious contract can exploit this by using a fallback function to re-enter createStaking, creating multiple staking contracts or draining funds. This can lead to unexpected state modifications and financial losses. To mitigate this, OpenZeppelin’s ReentrancyGuard should be used with the nonReentrant modifier, preventing recursive calls and ensuring the function executes only once per transaction, securing fund transfers and contract integrity.
low Issues | 3 findings
Resolved
#1 low 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.
Resolved
#2 low Issue
Missing zero or dead address check.
It is recommended that the address be checked to ensure that it can not be set to zero or dead.
Acknowledged
#3 low Issue
Lack of Upper Limit on msg.value
The createStaking function lacks an upper limit on msg.value, allowing users to accidentally send excessive funds, which are forwarded to _params.deployer without validation. This can lead to unintended financial losses if users mistakenly send large amounts of Ether. Additionally, it may be exploited by attackers attempting to manipulate fund flows. To mitigate this, a maximum fund limit (e.g., MAX_FUND_TRANSFER) should be enforced, rejecting transactions exceeding the limit. Adding if (msg.value > MAX_FUND_TRANSFER) revert StakingFactory__ExcessiveFunds(); ensures controlled fund transfers, preventing accidental losses and protecting users from potential exploitation.