AvaBot
- Completed
Project Information
-
Commissioned
02 Jan 2024
Completed
29 Jan 2024
Contracts Audited
AvaBot* 0x9f71B3118d97a448B127bf7677a59AB7454D0a04 AvaBotRouter 0xbDbE51B4206a7677039c1b7b9d6b0E31159C9C99 PaymentSplitter 0x27B0DDB09157171316089eBAFBe5E7DFf8979C5e TJRouter 0x2FF23Cf639c18Ad49E50E89e10f0b59F147788b0 View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)Governance
1 – – 1 High
2 1 1 – Medium
5 5 – – Low
8 1 – 7 Informational
9 6 – 3 Total 25 13 1 11 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.