unshETH
- Completed
-
Audit Report
Commissioned
20 May 2023
Completed
15 Jun 2023
Contracts Audited
ERC20PermitPermissionedMint Dependency unshETH 0x0Ae38f7E10A43B5b2fB064B42a2f4514cbA909ef Darknet 0x1a890EBCD20a9fB551C0440428805BC24eF62641 LSDVault 0x51A80238B5738725128d3a3e06Ab41c1d4C05C74 RenouncedOwner 0xb250216b5bcE306Fa37F7DE76A82409663eD52c3 unshETHZap 0xc258fF338322b6852C281936D4EdEff8AdfF23eE vdAMM 0x35636B85B68C1b4A216110fB3A5FB447a99DB14A Owned Dependency View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)High 0 – – – Medium 6 3 2 1 Low 9 1 2 6 Informational 17 2 – 15 Total 32 6 4 22 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.