Brewlabs
- Completed
-
Audit Report
Commissioned
12 Aug 2023
Completed
05 Oct 2023
Contracts Audited
BrewlabsERC20 Dependency in BrewlabsFactory BrewlabsFactory 0xFe2bF5fc2D131dB07C5Ef7076856FD7f342738fF BrewlabsNFTDiscountManager 0xA681C75FF9976F8559e2Ca14e7b42BD9746A53d9 BrewlabsPair 0x13bBDBB16DE07F4dc10c773061da92F4002Fde1E Also dependency in BrewlabsFactory BrewlabsRouter 0x5c71e01556b01B6346a4435B145a15aA3A957D23 BrewlabsSwapFeeManager Proxy 0x9dF9d5A7597cd4BF781d4FA9b98077376F6643AD Implementation 0x9dF9d5A7597cd4BF781d4FA9b98077376F6643AD BrewlabsLibrary Dependency in BrewlabsRouter The team made some changes to BrewlabsSwapFeeManager and BrewlabsLibrary which we did not check, so the deployed code for those two contracts do not match the ones we have audited.
View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)Failed Resolution Governance 2 1 – 1 – High 5 2 2 – 1 Medium 3 1 1 1 – Low 9 8 – 1 – Informational 9 5 3 1 – Total 28 17 6 4 1 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.