As of 19 Nov 2026, Solv Protocol has 6 audit reports by 3 security firms on Trustblock; the latest is by Quantstamp, dated 15 Dec 2025. Those reports list no open critical findings. It also holds 2 deployed contracts on 1 chain.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Newest first
| Report | Security firm | Date | Scope | Critical findings | Source |
|---|---|---|---|---|---|
| Solv Protocol - BTC Redemption | Security firm: Quantstamp | Date: | Scope: —Not recorded; see the report | None open | certificate.quantstamp.com ↗ |
| Audit Report (SolvBTC) | Security firm: Paladin | Date: | Scope: 2 addresses on Ethereum | None open | IPFS ↗ |
| Solv Protocol - SolvBTC | Security firm: Quantstamp | Date: | Scope: Repository at commit eafc741 | None open | certificate.quantstamp.com ↗ |
| Solv Yield - Bearing Tokens | Security firm: CertiK | Date: | Scope: Files listed | None open | skynet.certik.com ↗ |
| Solv Protocol- Vault Guardian | Security firm: Quantstamp | Date: | Scope: Repository at commit 80300ac | None open | certificate.quantstamp.com ↗ |
| Solv Protocol stUSD - Audit | Security firm: CertiK | Date: | Scope: Files listed | None open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed | Mitigated |
|---|---|---|---|---|
| Critical | 0 | 0 | 0 | 0 |
| High | 2 | 1 | 4 | 0 |
| Medium | 1 | 0 | 3 | 2 |
| Low | 4 | 11 | 15 | 0 |
Marked Informational by the firms. 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.
Open the reportCurrently, some of the ACL implementations that allow token whitelisting only allow them to be added via `_addTokenWhitelist()` during deployment. There is no way to modify this token whitelist following deployment. This could be an issue if one of the tokens becomes compromised or is no longer supported, or, if there are additional tokens that would want to be supported by Solv in the future.
Open the reportWhen `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`.
Open the reportThe `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.
Open the reportThe `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.
Open the report"Dead" code refers to code which is never executed and hence makes no impact on the final result of running a program. Dead code raises a concern, since either the code is unnecessary or the necessary code's results were ignored. There is dead code in the following places: 1. `ETH` in `ERC20ApproveAuthorization` 2. `ETH` in `ERC20TransferAuthorization` 3. `GLP_REWAED_ROUTER` in `GMXV1AuthorizationACL` 4. `repayWithBalance()` in `SolvOpenEndFundAuthorizationACL`
Open the reportCurrently, the `SolvOpenEndFundAuthorization` does not initialize with support for the `repayWithBalance()` function despite that function being included in the `SolvOpenEndFundAuthorizationACL`.
Open the reportThe owner of the contracts can call `transferGovernance()` to transfer the ownership to a new address. If an uncontrollable address is accidentally provided as the new owner address, then the contract will no longer have an active owner, and functions with the `onlyGovernor()` modifier can no longer be executed.
Open the reportAs it presently is constructed, the contract is vulnerable to the [allowance double-spend exploit](https://github.com/comitylabs/openzeppelin-contracts/blob/6bd6b76d1156e20e45d1016f355d154141c7e5b9/contracts/token/ERC20/IERC20.sol#L43), as with other ERC20 tokens.
Open the report`GMX_REWAED_ROUTER_V2` and `GMX_REWAED_ROUTER` in`GMXV1Authorization`.
Open the reportThe `_allowedContractToFunctions` stores a mapping of allowed contracts and their corresponding allowed function selectors, while the `_contractACL` mapping stores target contract addresses and corresponding ACL contract addresses. One can add an address to `_contractACL` mapping via `setContractACL()`, but the function does not check if that target contract address is already in `_allowedContractToFunctions`, which is essential, as unless the contract is in that mapping, the flow will never reach the `_contractACL`.
Open the reportEvery Solidity file specifies in the header a version number of the format `pragma solidity (^)0.8.*`. The caret (`^`) before the version number implies an unlocked pragma, meaning that the compiler will use the specified version _and above_, hence the term "unlocked".
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x2265…8a680x2265a8e449ea5ff78ee4c115370e9b5957358a68 | Chain: Ethereum | Source code: Verified source |
| 0xb129…6e8e0xb12979ff302ac903849948037a51792cf7186e8e | Chain: Ethereum | Source code: Verified source |
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="solv-protocol"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
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