Solv Protocol - SolvBTC

QuantstampRepository at commit eafc741

Audit

Quantstamp reviewed Solv Protocol (Solv Protocol - SolvBTC) on 15 Aug 2024: 7 findings, 0 critical; 3 marked fixed, 3 acknowledged, 1 open.

No open critical findings
Open the reportOpen Solv Protocol’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings7

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium100
Low033
LowOracle May Return Outdated Nav InformationAcknowledged

The `getNav()` function of `SolvBTCYieldTokenOracleForSFT` returns the latest NAV of the specified ERC-20 token but ignores the latest set NAV time. Without validating that the returned NAV time is within a reasonable range, there may be risks of using outdated information. An outdated NAV value may affect the conversion rate between shares and assets of a `SolvBTCYieldToken`.

LowPotential Mismatch in `beacon` ContractAcknowledged

When calling `importProductProxy()`, the `productTypes[productType_].beacon` may be different from the beacon address used by the imported proxy. Therefore, the imported proxy may not upgrade since it is pointing to a different beacon.

LowUnimplemented Interfaces in `SolvBTCMultiAssetPool`Acknowledged

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.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (5)

  • https://github.com/solv-finance/SolvBTC/contracts/SftWrappedTokenFactory.sol at commit eafc741
  • https://github.com/solv-finance/SolvBTC/contracts/SolvBTCMultiAssetPool.sol at commit eafc741
  • https://github.com/solv-finance/SolvBTC/contracts/SftWrapRouter.sol at commit eafc741
  • https://github.com/solv-finance/SolvBTC/contracts/SolvBTCYieldToken.sol at commit eafc741
  • https://github.com/solv-finance/SolvBTC/contracts/SolvBTC.sol at commit eafc741

Part of Solv Protocol’s security record

Solv Protocol
Audits6 audits by 3 firmsLast audit Dec 2025, by Quantstamp.
Critical findingsNo open critical findingsAcross 6 reports.
Open Solv Protocol’s security record

Security firm

Quantstamp

236 projects reviewed · 332 reports · latest Oct 2026

See Quantstamp’s audits

Something 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