FBTC
Bounty Range
$1,000 - $100,000
external program
FBTC
FBTC is a decentralized protocol that enables the seamless transfer and management of Bitcoin (BTC) across various blockchain networks. By leveraging advanced cryptographic techniques and decentralized governance, FBTC ensures the security, efficiency, and interoperability of BTC assets within the broader blockchain ecosystem.
For more information about FBTC, please visit https://fbtc.com/
FBTC provides rewards in USDC/USDT on Ethereum, denominated in USD.
Smart Contract
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $100,000.
Minimum reward to discourage security researchers from withholding a bug report: $20,000
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 100,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 20,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack is eligible for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 10,000 to USD 25,000 depending on the funds at risk, capped at USD 25,000.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24 hours that the funds are temporarily frozen, up to the maximum high reward cap of USD 25,000. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
Participants must adhere to the Eligibility Criteria.
KYC (Know Your Customer) information submission is a requirement for payout processing.
Proof of Concept: Proof of concept is always required for all severities.
Responsible Publication: Category 3: Approval Required
Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
Any testing with pricing oracles or third-party smart contracts
Attempting phishing or other social engineering attacks against our employees and/or customers
Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
Any denial of service attacks that are executed against project assets
Automated testing of services that generates significant amounts of traffic
Public disclosure of an unpatched vulnerability in an embargoed bounty
Any other actions prohibited by the Immunefi Rules
FBTC's completed audit reports can be found at https://github.com/fbtc-xyz/fbtc-contract/tree/main/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
| Auditor | Link | Completed at |
|---|---|---|
| All Audits | https://github.com/fbtc-xyz/fbtc-contract/tree/main/audits | 20 December 2024 |
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report: