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 |
MediumCentralization risksFireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportMediumLack of chains whitelistingFireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportMediumIncorrect implementation of confirmCrosschainRequest() for destination chain validationFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportMediumMinting fee is not supposed to be charged to users and it is against protocol whitepaperFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowDifferent ownable contracts are used (Ownable, Ownable2Step)FireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportLowInvalid parameter handling in view functionsFireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportLowMisleading range / incorrect error message in getRequestsByIdRangeFireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportLowThe getFee function does not raise an exception if the configuration is not defined.FireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportLowZero address feeRecipient riskFireBTC FBTC security audit · MixBytes · 26 Jun 2024Fixed
The report gives no description here.
Open the reportLowConsider using OpenZeppelin's SafeCast library to prevent unexpected overflows when downcastingFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportShow 10 more
LowDisable renounce of ownership in contractsFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowFloating solidity pragma version should not be used in contractsFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowImproper Initialization of bytes32[] Array Leading to Failure in getRequestsByHashes FunctionFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowLack of checking for key parametersFBTC & Fire Bridge Contracts audit · BlockSec · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowLack of Target Chain Validity VerificationFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowLack of verification for the target chain in cross-chain requestsFBTC & Fire Bridge Contracts audit · BlockSec · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowNo Upper Limit for feeFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowOwnership change should use two-step processFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowPotential front-running DoS attackFBTC & Fire Bridge Contracts audit · BlockSec · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowUnhandle the result of confirmCrosschainRequest()FBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportShow 2 more
LowUnnecessary check in fireBridge.confirmCrosschainRequest()FBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
The report gives no description here.
Open the reportLowUse require instead of assertFBTC competitive security assessment · Secure3 · 20 Jun 2024Fixed
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