Quantstamp reviewed saffron.finance (Saffron) on 13 Jan 2023: 5 findings, 0 critical; 2 marked fixed, 3 acknowledged.
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 |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 3 | 2 |
Marked Informational or Undetermined by the firm. Not counted as findings.
Setter functions can emit duplicated events that may confuse external systems when the new value is equal to the old value: 1. `VaultFactory.setDefaultDepositTolerance()` 2. `VaultFactory.setFeeReceiver()` 3. `VaultFactory.setFeeBps()`
When a vault is created, if the fixed side reward is of high value, another user can front-run the vault creator and become the fixed side depositor, hence stealing opportunity from the vault creator. This will create a race condition where users will try to take a lucrative vault, even if the vault creator intended it for himself.
The clone-and-own approach involves copying and adjusting open source code at one's own discretion. From the development perspective, it is initially beneficial as it reduces the amount of effort. However, from the security perspective, it involves some risks as the code may not follow the best practices, may contain a security vulnerability, or may include intentionally or unintentionally modified upstream libraries. Use Uniswap's `FullMath.sol` instead of `Math.sol` to avoid maintaining the code.
`UniV3LimitedRangeAdapter.removeLiquidity()` should require that earning have been settled. Safety checks must be implemented at the smart contract level to prevent future breaking changes. Similarly, `UniV3LimitedRangeAdapter.deployCapital()` should require that the token ID is not set in order to safely execute the transaction..
As security standards develop, so does the Solidity language. To stay up to date with current practices, it's important to use a recent version of Solidity and recent conventions.
Local variable naming in `UniV3LimitedRangeAdapter.mintToken()` is confusing: ``` (..., uint256 minted0, uint256 minted1) = positionManager.mint(params); ``` `minted0` and `minted1` do not represent minted amounts but the amount used as liquidity for the Uniswap pool.
Every 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".
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (22)
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