Solv Protocol - BTC Redemption

QuantstampCode version: not recorded (see the report)

Quantstamp reviewed Solv Protocol (Solv Protocol - BTC Redemption) on 15 Dec 2025: 3 findings, 0 critical; all acknowledged, none fixed.

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

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings5

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low030

Marked Informational by the firm. Not counted as findings.

InformationalMissing Event Emission When `pendingAdmin` Is ClearedFixed

When `acceptAdmin()` is called, the `pendingAdmin` variable is deleted without emitting an event that reflects its change to the zero address. While a `NewAdmin` event is emitted for the admin change, the lack of an explicit event for the `pendingAdmin` update can lead to inconsistencies for off-chain indexers or monitoring systems that rely on events to track the lifecycle of `pendingAdmin`.

InformationalWithdraw Fee Rate Has No Explicit Upper BoundFixed

The `withdrawFeeRate` parameter has no explicit upper bound enforced at the contract level. Although the calculation includes a safety check: `require(withdrawFee <= solvBTCAmount_)` this still allows configurations where the effective fee can approach 100% of the redemption amount, effectively resulting in near-zero `solvBTC` output for users, minimizing withdrawals amount for all users.

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.

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

240 projects reviewed · 338 reports · latest Nov 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