Function security record
As of 19 Oct 2026, Function has 1 audit report on Trustblock, by MixBytes, dated 26 Jun 2024. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits3
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| FireBTC FBTC security audit | Security firm: MixBytes | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| FBTC competitive security assessment | Security firm: Secure3 | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| FBTC & Fire Bridge Contracts audit | Security firm: BlockSec | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
Findings34
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 4 | 4 |
| Low | 0 | 8 | 18 |
MediumThe _getFee function is not monotonicFireBTC FBTC security audit · MixBytes · 26 Jun 2024Acknowledged
The report gives no description here.
Open the reportMediumBlock Reorg Can Allow For Double SpendingFBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportMediumHave no refund mechanism for addBurnRequest() and addCrosschainRequest()FBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportMediumMinter can mint before withdrawal finality for l2 -> l1 transactions.FBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportLow_disableInitializers() can be usedFireBTC FBTC security audit · MixBytes · 26 Jun 2024Acknowledged
The report gives no description here.
Open the reportLowLack of validation for the zero-width fee tiersFireBTC FBTC security audit · MixBytes · 26 Jun 2024Acknowledged
The report gives no description here.
Open the reportLowCentralization riskFBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportLowCentralization RiskFBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportLowCentrazliation RiskFBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportLowFor loop gas optimization(All optimizations included)FBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportShow 2 more
LowIssues related to hardfork.FBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
Open the reportLowSet the Constant to PrivateFBTC competitive security assessment · Secure3 · 20 Jun 2024Acknowledged
The report gives no description here.
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="function"></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