Valley Swap
- Completed (2)
-
Audit Report
Commissioned
26 Jan 2022
Completed
16 Feb 2022
Contracts Audited
ValleySwapToken 0xBC033203796CC2C8C543a5aAe93a9a643320433D ValleySwapFarm 0xaE0aF27df228ACd8BA91AF0c917a31A9a681A097 Timelock 0xaA622C649F9F7EBe1dD05a8bD88549f616483495 View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 2 2 – – Medium 5 5 – – Low 4 4 – – Informational 5 4 – 1 Total 16 15 – 1 -
Audit Report (AMM)
Commissioned
26 Jan 2022
Completed
16 Mar 2022
Contracts Audited
ValleySwapRouter 0x7C0b0a525fc6A2caDf7AE37198119025C6feA28a ValleySwapPair Created by ValleySwapFactory ValleySwapFactory 0xa25464822b505968eEc9A45C43765228c701d35f ValleySwapLibrary 0x35Cb221C896CfEbd4Bc6150E6Eb93f8a83E1D395 Math, UQ112x112 Dependency View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 2 2 – – Medium 0 – – – Low 0 – – – Informational 5 3 – 2 Total 7 5 – 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.