專案簡介
The target of this audit is the private code repository of Composer Contracts of Inverter Network. Composer Contracts of Inverter Network implement a LayerZero-based staking and bridging system for emUSD, refactored from the earlier iTry cross-chain architecture. Users deposit emUSD into the wemUSD vault in exchange for yield-bearing shares and can exit through cooldown-based unstaking or fast redemption. The system supports both hub-local and cross-chain deposits, redemptions, and unstake claims: emUSD is bridged through a burnand-mint OFT, while wemUSD is transferred through a canonical-share adapter. It additionally provides a cross-chain retirement flow that burns wemUSD shares and confirms the corresponding emUSD burn for the retirement of the relevant RWA position.
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.
關鍵發現
我們在該智能合約中共發現 2 個潛在問題,另有 2 條建議與 3 條說明,明細如下:
| ID | Severity | Description | Status |
|---|---|---|---|
| 1 | Low | Potential DoS due to the donation attack in the contract EmAssetForfeitComposer |
Fixed |
| 2 | Low | Lack of rate limit checks when initiating cooldown requests | Confirm |
| 3 | - | Use Ownable2Step for ownership transfer in the contract EmAssetForfeitComposer |
Fixed |
| 4 | - | Add slippage protections in the contract EmAssetVaultComposer |
Fixed |
| 5 | - | Potential centralization risks | - |
| 6 | - | Properly deploy OFT adapter contracts | - |
| 7 | - | Set peers correctly for each OApp contract |
- |
更多細節見審計報告。