Flare is the blockchain for data. It is a layer-1, EVM smart contract platform designed to expand the utility of blockchain by delivering data certainty for dApp builders.
FAssets is a trustless, over-collateralized bridge built on Flare that connects non smart contract networks to Flare/Songbird. It enables the creation of wrapped tokens (FAssets) for assets like BTC, DOGE and XRP.
Triaged by Immunefi
PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
- Impacts achieved with frontrunning attacks will have severity lowered by one level.
- Impacts requiring malicious agent actions will have severity lowered by one level.
- Theft, freezing or loss of dust amounts of funds below the value of $1000 will be considered as griefing.
- Loss of funds caused by penalisation is not considered as theft of funds.
Protocol insolvency
Ability to exfiltrate agent bot’s private keys
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Unauthorized minting of FAssets or collateral tokens
Temporary freezing of funds
Theft of unclaimed yield
Stealing funds from any FAsset bot
Bot fails to deliver expected functionality, leading to loss of funds (e.g. by entering full liquidation or defaulting redemptions)
Unauthorized freezing of unclaimed yield
Manipulation of redemption or minting processes, causing users to receive incorrect amounts
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Bot fails to deliver expected functionality, no funds at risk
Out of scope
The FAssets system is able to support wrapped tokens for XRP, BTC and DOGE. However, the initial deployment will only have XRP (FXRP) enabled. Any attacks related to FBTC, FDOGE, or UTXO-based logic in general, are out of scope.
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers