Quantstamp reviewed Solv Protocol (Solv Protocol - SolvBTC) on 18 Jul 2024: 4 findings, 0 critical; 2 marked fixed, 2 acknowledged; 1 more marked mitigated.
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 | Mitigated |
|---|---|---|---|---|
| Critical | 0 | 0 | 0 | 0 |
| High | 0 | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 | 1 |
| Low | 0 | 2 | 2 | 0 |
Marked Informational by the firm. Not counted as findings.
According to the protocol design, the `SolvBTCMultiAssetPool` contract may receive ERC-3525 tokens. Therefore, it is best practice to implement the ERC-165 interface and define the `onERC721Received()` and `onERC3525Received()` functions to return the corresponding magic values. Some SFT implementations, such as `OpenFundShareDelegate`, allow the ERC-3525 receiver to revert on the ERC-165 `supportsInterface()` call and consider the receiver capable of receiving ERC-3525 tokens. However, this behavior is not guaranteed in other SFT implementations.
The `admin` of the `SftWrappedTokenFactory` contract can upgrade the implementation contract for a given `productType_` by calling `setImplementation()` followed by a call to `upgradeBeacon()`. However, if `upgradeBeacon()` is not called, the `productTypes` mapping in the `SftWrappedTokenFactory` contract will have a mismatched `implementation` address than what is set in the beacon contract.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (5)
240 projects reviewed · 338 reports · latest Nov 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