In some cases, only the proxy contracts are listed as in-scope; however, current implementation and any further updates to the implementation are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target. 

All smart contracts of Flux Finance can be found at [https://github.com/flux-finance/contracts](https://github.com/flux-finance/contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. 

If an impact can be caused to any other asset managed by Flux Finance that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. 


Flux Finance is a decentralized lending protocol built by the Ondo Finance team.

Any governance voting result manipulation

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Miner-extractable value (MEV)

Temporary freezing of funds for at least 24 hours

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Smart contract unable to operate due to lack of token funds

Smart contract fails to deliver promised returns, but doesn't lose value

Rewards are distributed according to the impact of the vulnerability based on the[  Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. 

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. Bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 25 000 for Critical smart contract bug reports.

The following known issues are also considered out of scope of this program:
- Effects from blacklists (e.g. KYC revoked, USDC blacklist), if the effect only impacts the specific user.
- Effects from using hypothetical use of tokens that do not follow the ERC-20 standard or include unusual behavior (e.g. transfer tax). If a token has certain functionality but that functionality is currently disabled, the effect will also be considered out of scope.
- Misuse of admin rights (e.g. malicious admin multi-sig)
- The protocol is forked from CompoundV2. The fToken contracts are forked from this [commit](https://github.com/compound-finance/compound-protocol/tree/a3214f67b73310d547e00fc578e8355911c9d376). All other contracts (Comptroller, CErc20Delegator, InterestRateModel, etc.) are forked from this [commit](https://github.com/compound-finance/compound-protocol/tree/3affca87636eecd901eb43f81a4813186393905d). Bug reports covering previously-discovered bugs are not eligible for the program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report. Previous audits of CompoundV2 can be found at: [https://docs.compound.finance/v2/security/#audits](https://docs.compound.finance/v2/security/#audits)
- Any known issues in CompoundV2 up to these commits are considered out of scope. This includes, but is not limited to:
   - First deposit bug when a market is initialized - example [video](https://youtu.be/_pO2jDgL0XE?t=157)
   - Discrepancy in borrow rate per block on-chain vs. displayed APY in the UI

Payouts are handled by the __Flux Finance__ team directly and are denominated in USD. However, payouts are done in __USDC__.  The payment will be made by Flux Finance (the entity).


Flux Finance

Resources & Documentation