DESCRIPTION
The target of this audit is the private code repository of rNEAR Contract of Rhea Finance. The project is deployed on the NEAR network. Users can deposit NEAR into the protocol, which mints a corresponding amount of rNEAR based on the current share price. Conversely, users can also unstake by burning their rNEAR in exchange for the corresponding amount of NEAR. Users holding rNEAR receive PoS rewards.
Please refer to the report for the detailed audit scope.
Our audit methodology employs automated vulnerability scans, manual verification, and business logic analysis to uncover potential security issues coupled with gas and code quality optimization recommendations.
In summary, we have found that the codebase contains 3 high-risk issues that require prompt attention. In addition, we have identified other non-critical issues as well as recommendations and notes that should be considered. The rNEAR Contract team has addressed these issues promptly. It is important to note that our audit covers only the final reported versions of the codebase. Any subsequent updates would require a re-evaluation.
KEY FINDINGS
In total, we find 5 potential issues in the smart contract. We also have 1 recommendations and 3 notes, as follows:
| ID | Severity | Description | Status |
|---|---|---|---|
| 1 | High | Incorrect logic in deposit operations | Fixed |
| 2 | High | Incorrect rewards distribution for beneficiary | Fixed |
| 3 | High | Validator pool lock due to unhandled callback and reward minting failure | Fixed |
| 4 | Low | Lack of executing status check in function remove_validator() |
Fixed |
| 5 | Low | Improper external method invocation in function drain_unstake() |
Confirm |
| 6 | - | Lack of one yocto check in privileged functions | Fixed |
| 7 | - | Potential centralization risk | - |
| 8 | - | Ensure timely invocation of function epoch_update_rewards() |
- |
| 9 | - | Potential arbitrage opportunity | - |
More details are provided in the audit report.
