專案簡介
The target of this audit is the private code repository of puffer-institutional of Puffer. 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 did not find any critical issues within the audited codebase. However, we have identified some non-critical issues that should be addressed. Additionally, we have put forth recommendations and notes that should be taken into consideration. It is important to note that the scope of our audit was strictly limited to the specific code versions mentioned in the report. Any updates made subsequent to our review would require a re-evaluation.
關鍵發現
我們在該智能合約中共發現 3 個潛在問題,另有 5 條建議與 9 條說明,明細如下:
| ID | Severity | Description | Status |
|---|---|---|---|
| 1 | Low | Incorrect reward accounting | Confirmed |
| 2 | Low | Potential front-running attack | Confirmed |
| 3 | Low | Incorrect accounting of nonRestakedValidatorsETH |
Confirmed |
| 4 | - | Align documentation with implementation | Fixed |
| 5 | - | Add non-zero checks on deposits and withdrawals | Fixed |
| 6 | - | Emit native exit events | Fixed |
| 7 | - | Add a non-zero check on the receiver |
Fixed |
| 8 | - | Validate the deposit amount and public key length | Confirmed |
| 9 | - | Potential centralization risks | - |
| 10 | - | Share price dependence on reported validator balances | - |
| 11 | - | Atomic upgrade and initialization | - |
| 12 | - | Withdrawal error selector compatibility | - |
| 13 | - | Authority migration for the withdrawal credentials contract | - |
| 14 | - | Trust assumptions of Oracle roles | - |
| 15 | - | Ensure pending rewards are reported | - |
| 16 | - | Fee mechanisms are controlled by institutions | - |
| 17 | - | Ensure correct handling of validator consolidations | - |
更多細節見審計報告。