Resonance Security reviewed RTLabs on 31 Aug 2024: 13 findings, 1 critical; 12 marked fixed, 1 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 | 0 | 1 |
| Medium | 0 | 0 | 5 |
| Low | 0 | 1 | 5 |
Marked Info by the firm. Not counted as findings.
Smart contract upgradeability using OpenZeppelin's standard, requires contracts to use initializer functions. The function to use on child contract should be named initialize() and should possess the initializer modifier, while parent contracts should have _init() and _init_unchained() functions with the modifier onlyInitializing, where there would otherwise be constructors called automatically on non-upgradeable smart contracts.The initializer functions on the parent smart contracts are meant to be initialized by the child contract, as such, their visibility can be constrained to internal. The following functions do not implement the proper visibility to encourage a principle of least privilege:The visibility of the function __OwnableAccessControl_init() is incorrectly set as public.
The functions _init() and _init_unchained() are an implementation of OpenZeppelin's Upgradeable Proxies design standard and are used to serve as the constructor of upgradeable contracts. Despite being both used as initializers, they possess slightly different use cases to correctly implement the analog linearization of smart contract constructors.The function _init() should be used and implemented to embed the linearized calls to all parent initializers. The function _init_unchained() should be used to perform the initialization of the variables for the current contract only.As a consequence of this design, it is possible that, due to the lack of automatic linearization, the calling of _init() functions initializes the same contract multiple times. For these cases, the _init_unchained() function may be used manually to avoid double initialization, however it will break the upgradeability design and compatibility between smart contracts on the blockchain.Additionally, the inherited smart contracts should be initialized according to their inheritance order, from the most base-like to the most derived.There are multiple instances where contracts do not follow the design standard in the following account:_init_unchained() function is not used.Initialization according to inheritance order is incorrect
Throughout the source code of the protocol, there are several instances where uint256 variables are being compared to 0. The comparison of these variables being lesser than or equal to 0 is redundant as uint256 variables can only contain 0 or positive values.
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