Pandora Swap
- Completed
-
Audit Report
Commissioned
27 Apr 2022
Completed
29 Apr 2022
Contracts Audited
PandoraToken 0x8ea356004327E598729b4CE590eDC90428Dc6A89 PandoraRouter02 0x0fd60f0B13F7d816aE2DF1B9a4B62a9d94FbCac5 PandoraFactory 0x8D4f9b98FC21787382647BFCfC9ce75C08B50481 Masterpandora 0x894d03D77b42bBeC83CEe221596ba17a83b995eC ProxyPandora Proxy 0xFAD2dB84ec6b6496544FE9E34db2EBAee17eB691 Implementation 0xc05a719138Ca3d0F63b4636CbDD99f40E4953fdc Referral 0x1313bF6D51026CDaD577ac09D19A498aE044d37f View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High 1 1 – – Medium 2 – 1 1 Low 9 1 1 7 Informational 27 1 2 24 Total 39 3 4 32 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.