FAssets
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.
Triaged by Immunefi
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Ability to exfiltrate agent bot’s private keys
Direct theft of any user/system funds, whether at-rest or in-motion (excluding attacks by agents)
Protocol insolvency resulting in the inability to fulfill system-wide redemption requests or honor collateral guarantees.
Unauthorized minting of FAssets or collateral tokens
Theft of user/system funds by an agent, beyond their backed capacity.
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)
Theft of unclaimed yield/rewards (e.g., rewards intended for FAsset holders, or collateral providers)
Theft of user/system funds by an agent, within their backed capacity.
Protocol insolvency resulting in the inability to fulfill agent-bound redemption requests or honor collateral guarantees.
Unauthorized freezing of unclaimed yield
Preventing participants from minting, redeeming or transferring FAsset tokens
Out of scope
Smart Contract 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