Usual
- Completed
-
Audit Report
Commissioned
02 Oct 2024
Completed
03 Oct 2024
Contracts Audited
L2Usd0 Proxy: 0x35f1C5cB7Fb977E669fD244C567Da99d8a3a6850 Implementation: 0x7497537F62eFd47aCfFF3D0942127650dA40c167 L2Usd0PP Proxy: 0x2B65F9d2e4B84a2dF6ff0525741b75d1276a9C2F Implementation: 0x1EaCc08C0a4a059D1567a587ed9D0a52eAC2A88F View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)Governance
2 – – 2 High
0 – – – Medium
0 – – – Low
1 1 – – Informational
5 5 – – Total 8 6 – 2 When using this protocol, the main risks you want to look out for are:
- Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
- Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.