.svg)
Summary
The most critical subjects covered in our audit are functional correctness, manipulation resiliency and the integration of the CapAutomator into the existing SparkLend protocol. A notable issue was identified in the original code where setting caps to zero is not restricted, leading to the potential bypass of the cooldown period and risks of lifting the cap (see Cap of 0 ignores increase cooldown). After the intermediate report, all identified issues have been addressed or acknowledged. The general subjects covered are optimizations and adherence to the specifications
In summary, we find that the codebase provides a good level of security.
It is important to note that security audits are time-boxed and cannot uncover all vulnerabilities. They complement but don’t replace other vital measures to secure a project.
About SparkLend cap automator
SparkLend CapAutomator manages supply and borrow caps for assets in SparkLend. In the latest reviewed version, it allows updaters to trigger updates to these caps based on predetermined parameters, with the new cap values calculated using the current supply and a specified gap, subject to maximum limits and cooldown periods.