Quantstamp reviewed Zoro Protocol on 31 Jan 2024: 6 findings, 0 critical; 2 marked fixed, 3 acknowledged, 1 open.
Report hosted on certificate.quantstamp.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 3 | 2 |
The `borrowRateMaxMantissa` is used as an upper bound for the borrowing rate and initialized to `0.0005e16`, or 0.0005% per block. However, this value was determined based on the L1 block times of roughly 12 seconds. With interest now accruing every second rather than every block, this upper bound allows for a far higher borrowing rate.
The `transfer()` call for sending native tokens to `msg.sender` in the `Maximillion.repayBehalfExplicit()` function has been re-written to `.call()` to be compatible with zkSync and also as a best practice. However, the return value of the `call()` function is not checked to be `true`. In case `msg.sender` reverts the transaction in its `fallback()` or the `receive()` function for any reason (e.g., developers forget to define a payable fallback function), the native tokens will be locked in the `Maximillion` contract permanently, as there is no other way to retrieve the funds.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (30)
236 projects reviewed · 332 reports · latest Oct 2026
See Quantstamp’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us