Musing
- Completed
-
Audit Report
Commissioned
Completed
16 May 2024
Contracts Audited
ERC20Initializable Dependency MerkleDistributor 0xB7afF81b38Bd628E58AF8667E390Fa45914008A4 BulkTransfer 0x8a008A50A0482Fd69d7f0B0e2ceb5358961d11c5 Royalty Dependency Token 0x035B5b6cd455d65a04c182bED7E14aA8A0254478 MSCBond 0x809dC9E06122b3f433ebfA0B0ef013073BBb4805 Zap 0xDA1e0cbbC40a601C35c88EA5446267CdBe259bc9 View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)Governance 0 – – – High 2 1 – 1 Medium 2 1 – 1 Low 5 3 – 2 Informational 10 5 1 4 Total 19 10 1 8 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.