Quantstamp reviewed Sapien on 30 Mar 2025: 14 findings, 0 critical; 9 marked fixed, 5 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 | 2 |
| Medium | 0 | 2 | 4 |
| Low | 0 | 3 | 3 |
Currently, the function `calculateMultiplier()` will always return the `maxMultiplier` if the following condition is true: ``` if (amount >= BASE_STAKE) { return maxMultiplier; } ``` However, this condition will always be true, since during staking, it is required that the amount staked be greater than the `BASE_STAKE`: `require(amount >= BASE_STAKE, "Amount must be greater than base stake");`
The `recoverSigner()` function in the `Rewards` contract uses the `ecrecover` precompile which is vulnerable to signature malleability. This vulnerability allows multiple valid signatures to be generated for the same message, as ecrecover accepts signatures with both high and low values of the s parameter. While this would typically be a high-severity issue that could allow signature replay attacks, the severity is significantly reduced because the function is currently unused in the contract. But since the contract is upgradeable consider fixing this issue to avoid impacting newer versions.
The function `SapienStaking.calculateMultiplier()` awards the same multiplier for a very wide range of stake amounts. One such example of this is that any `amount` from 980 tokens up to 999.999999999999999999 tokens will receive a multiplier of 149. This creates a large "dead zone" where users get no benefit from staking additional tokens, followed by a sharp cliff where 1 wei more suddenly increases the multiplier.
According to the README, the test suite can be executed by running `npx hardhat test`. However, the test are actually written with the syntax expected by Truffle, not hardhat. As a result the above mentioned command throws an error. Unfortunetaly, using Truffle does not work either since running `truffle test` also throws an error.
The `releaseTokens()` function transfers the tokens from the `gnosisSafe` (who originally got all the token supply) to the `schedule.safe` address which originally was set as the same `gnosisSafe`. This could lead to the contract and the original receiving team thinking that a vesting was succesfully released when the original owner of the token still has them.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (3)
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