As of 19 Nov 2026, Sapien has 2 audit reports by 1 security firm on Trustblock; the latest is by Quantstamp, dated 2 Jul 2025. Those reports list no open critical findings.
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 |
|---|---|---|---|---|---|
| Sapien - 2 | Security firm: Quantstamp | Date: | Scope: Files listed | None open | certificate.quantstamp.com ↗ |
| Sapien | Security firm: Quantstamp | Date: | Scope: Files listed | None open | certificate.quantstamp.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 6 |
| Medium | 0 | 2 | 6 |
| Low | 0 | 3 | 6 |
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");`
Open the reportThe `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.
Open the reportThe 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.
Open the reportAccording 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.
Open the reportThe `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.
Open the reportThe reports name a repository or files. Open a report to see its scope.
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="sapien"></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