
Everdawn
- Completed
-
Audit Report
Commissioned
04 Jan 2025
Completed
10 Jan 2025
Contracts Audited
OAdapterUpgradeable (ETH) Proxy: 0x6C96dE32CEa08842dcc4058c14d3aaAD7Fa41dee Implementation: 0xCD979B10A55FCdAC23ec785CE3066c6ef8a479A4 OUpgradeable (INK) Proxy: 0x1cB6De532588fCA4a21B7209DE7C456AF8434A65 Implementation: 0x2257df4b93d2A55ED553194cAbEcD851A346FF89 TetherToken Dependency EIP3009 Dependency TetherTokenV2 Dependency WithBlockedList Dependency ArbitrumExtension Not deployed CeloExtension Not deployed FeeCurrencyWrapper Not deployed OFTExtension Proxy: 0x0200C29006150606B650577BBE7B6248F58470c1 Implementation: 0x4a5cd36c33D9F2986e5d39fF5B9918af547a6e0E WrapperExtension Not deployed View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)High
0 – – – Medium
0 – – – Low
1 – – 1 Informational
11 1 2 8 Total 12 1 2 9 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.