FireBTC FBTC security audit
MixBytes reviewed Function (FireBTC FBTC security audit) on 26 Jun 2024: 10 findings, 0 critical; 7 marked fixed, 3 acknowledged.
No open critical findings
Open the reportOpen Function’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings10
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 1 | 2 |
| Low | 0 | 2 | 5 |
MediumCentralization risksFixed
The report gives no description here.
MediumLack of chains whitelistingFixed
The report gives no description here.
LowDifferent ownable contracts are used (Ownable, Ownable2Step)Fixed
The report gives no description here.
LowInvalid parameter handling in view functionsFixed
The report gives no description here.
LowMisleading range / incorrect error message in getRequestsByIdRangeFixed
The report gives no description here.
LowThe getFee function does not raise an exception if the configuration is not defined.Fixed
The report gives no description here.
LowZero address feeRecipient riskFixed
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
FunctionAudits1 audit by 1 firmLast audit Jun 2024, by MixBytes.
Critical findingsNo open critical findingsIn 1 report.
Open Function’s security recordSecurity firm
MixBytes
latest Jun 2024
See MixBytes’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