Resonance Security reviewed Primex Finance on 19 Oct 2023: 12 findings, 1 critical; 9 marked fixed, 3 acknowledged.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 1 | 0 |
| Medium | 0 | 2 | 4 |
| Low | 0 | 0 | 4 |
Marked Info by the firm. Not counted as findings.
The function batchBurn() does not validate whether the _amounts array contains elements with 0 amount, allowing transactions to take place and events to be emitted that do not change the state of the blockchain. This fact not only incurs unnecessary gas costs, but also fills the blockchain with unnecessary transactions,
Most supportsInterface() functions across the Primex protocol validate the base-most interfaceId. Due to both the inheritance nature of the Solidity language, and the short-circuiting capability of its logical operators, testing the base-most interface first is not optimal to save gas.
The function canBeFilled() implements several versions used throughout different contracts of the Primex protocol. Using different versions of code for the same intended behaviour may lead to unexpected and/or inconsistent results.
The function createBucket() correctly validates _params.positionManager and _params.reserve. However, this validation is unnecessary since the same validation is being made inside the contract Bucket, therefore leading to a duplication of code and the increase of gas costs.
The inclusion of unlimited approval in contracts increase potential attack surface.
The report names a repository or files. Open the report to see its scope.
27 projects reviewed · 57 reports · latest Dec 2025
See Resonance Security’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