FBTC competitive security assessment
Secure3 reviewed Function (FBTC competitive security assessment) on 20 Jun 2024: 21 findings, 0 critical; 12 marked fixed, 9 acknowledged.
Report hosted on GitHub.
Trustblock does not review code.
Findings21
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 3 | 2 |
| Low | 0 | 6 | 10 |
MediumIncorrect implementation of confirmCrosschainRequest() for destination chain validationFixed
The report gives no description here.
MediumMinting fee is not supposed to be charged to users and it is against protocol whitepaperFixed
The report gives no description here.
LowConsider using OpenZeppelin's SafeCast library to prevent unexpected overflows when downcastingFixed
The report gives no description here.
LowDisable renounce of ownership in contractsFixed
The report gives no description here.
LowFloating solidity pragma version should not be used in contractsFixed
The report gives no description here.
LowImproper Initialization of bytes32[] Array Leading to Failure in getRequestsByHashes FunctionFixed
The report gives no description here.
LowLack of Target Chain Validity VerificationFixed
The report gives no description here.
LowNo Upper Limit for feeFixed
The report gives no description here.
LowOwnership change should use two-step processFixed
The report gives no description here.
LowUnhandle the result of confirmCrosschainRequest()Fixed
The report gives no description here.
Show 2 more
LowUnnecessary check in fireBridge.confirmCrosschainRequest()Fixed
The report gives no description here.
LowUse require instead of assertFixed
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Part of Function’s security record
FunctionSecurity firm
latest Jun 2024
See Secure3’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