Bequest security record
As of 3 Nov 2026, Bequest has 2 audit reports by 1 security firm on Trustblock; the latest is by CertiK, dated 10 Mar 2023. 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.
Audits2
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Bequest Finance | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| Bequest Finance (Audit #2) | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
Findings10
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 4 |
| Low | 0 | 3 | 3 |
LowCheck Effect Interaction Pattern ViolatedBequest Finance · CertiK · 10 Mar 2023Acknowledged
The order of external call/transfer and storage manipulation must follow the check-effect-interaction pattern.[LINK](https://fravoll.github.io/solidity-patterns/checks_effects_interactions.html)
Open the reportLowPossibility to Bypass Distribution FeeBequest Finance · CertiK · 10 Mar 2023Acknowledged
Distribution fee may be bypassed by bequester. Function `distribute()` uses `safeSendERC20s()` to collect the distribution fees. Function safeSendERC20s() has the issue reflected in BWV-03, that the bequester could change the allowance to the `BequestWillV1` contract after the bequest becomes claimable. If the bequester set the allowance to 0 before the first `distribution()` call, he won't pay any distribution fees, and the first recipients won't receive any tokens. The bequester can then set the allowance back to normal to allow the normal bequest process. On the other hand, if the bequester is still able to reset the allowance after the bequest is claimable, he could simply transfer out the token without the bequest service.
Open the reportLowThird Party DependenciesBequest Finance · CertiK · 10 Mar 2023Acknowledged
The contract is serving as the underlying entity to interact with third party ERC20, ERC721 and ERC1155 at the bequest owners' choice. The scope of the audit treats 3rd party entities as black boxes and assume their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
Show this on your site
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.
Content
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="bequest"></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