![](https://paladinsec.co/pld/assets/BQVepreL_400x400-300x300.jpg)
Kalao Builder
- Completed
-
Audit Report: Kalao Builder
Commissioned
Completed
05 Apr 2022
Contracts Audited
RewardDistributor RewardDistributor.sol RewardRouter RewardRouter.sol RewardTracker RewardTracker.sol Vester Vester.sol Governable Governable.sol Preliminary https://github.com/kalaobuilder/stacking_contracts/tree/8eb3e40fa0de2cb6474a9ba8c2189c0530ccd90c Resolution https://github.com/kalaobuilder/stacking_contracts/pull/1 The project team did not get back to us with the deployed addresses, so users should check that the code of the contract they are interacting with matches the code in the resolution GitHub commit.
View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High
5 – – 5 Medium
3 – – 3 Low
5 – – 5 Informational
26 8 – 18 Total 39 8 – 31 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.