Project Information
Category
- Yield Farm
Network
- BSC
21 Aug 2021
25 Aug 2021
MerkleDistributor | MerkleDistributor.sol |
The client has commissioned Paladin to do a test-driven audit. This means that throughout the auditing process, the auditors created unit and integration tests to support the issues raised and to validate the functionality of the protocol. Paladin should not be seen as a contributor of the protocol in any way, shape or form. These tests are exclusively part of the audit process and thus fall under the same terms and conditions that govern the audit. They do not warrant acknowledgment of liability, contribution or similar to the protocol. The tests are simply provided as support for the findings within this audit.
Test-driven Audit
View Audit Report
Found | Resolved | Partially Resolved | Acknowledged (no change made) |
|
---|---|---|---|---|
1 | 1 | – | – | |
2 | 2 | – | – | |
5 | 3 | – | 2 | |
8 | 8 | – | – | |
Total | 16 | 14 | – | 2 |
When using this protocol, the main risks you want to look out for are:
Exploits, vulnerabilities or errors that will certainly or probabilistically lead towards loss of funds, control, or impairment of the contract and its functions. Issues under this classification are recommended to be fixed with utmost urgency.
Bugs or issues with that may be subject to exploit, though their impact is somewhat limited. Issues under this classification are recommended to be fixed as soon as possible.
Effects are minimal in isolation and do not pose a significant danger to the project or its users. Issues under this classification are recommended to be fixed nonetheless.
Consistency, syntax or style best practices. Generally pose a negligible level of risk, if any.