Composable Finance
Program Overview
Composable Finance is dedicated to improving the accessibility, quality, transparency, efficiency, and security of decentralized finance (DeFi). It aims to do this by pioneering innovative Web3 user experiences in a trustless, non-custodial, and decentralized manner. Composable's technology stack enables and combines key services across different DeFi ecosystems and protocols, such as Ethereum, Polkadot, Cosmos, and NEAR.
With their products, Composable Finance intends to reduce these barriers that DeFi developers and users face.
For more information about Composable Finance, please check out their website at https://www.composable.finance/ and their docs at https://docs.composable.finance/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the 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 Critical and High Blockchain/DLT 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.
Reward maximums vary case-by-case with direct regard to the impact of the threat presented and scoped as determined by Composable Finance personnel. Composable Finance offers varying guaranteed minimum payouts for all levels of vulnerabilities with an accompanying PoC. Reward maximums will not exceed $500,000.
Composable Finance requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are 2 forms of Photo Identification and Proof of Address. The collection of this information will be done by the project team.
Payouts are handled by the Composable Finance team directly and are denominated in USD. However, payouts are done in USDC.
Blockchain/DLT
- Critical
- Level
- USD $30,000 to USD $500,000
- Payout
- High
- Level
- USD $5,000 to USD $30,000
- Payout
- Medium
- Level
- USD $1,000 to USD $5,000
- Payout
Assets in scope
- Blockchain/DLT - PicassoType
All projects of Composable Finance can be found at https://github.com/ComposableFi. 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 Composable Finance that isn’t on this table but for which the impact is in the Impacts in Scope section below, and is classified as High or Critical, you are encouraged to submit it for the consideration by the project.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
Blockchain/DLT
- Network not being able to confirm new transactions (Total network shutdown)CriticalImpact
- Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)CriticalImpact
- Direct loss of fundsCriticalImpact
- Permanent freezing of funds (fix requires hardfork)CriticalImpact
- RPC API crash that causes severe or total disruptionCriticalImpact
- Ability to halt the chain or alter block productions / the network by providing bad input dataCriticalImpact
- Unintended chain split (Network partition)HighImpact
- Transient consensus failuresHighImpact
- High compute consumption by validator/mining nodesMediumImpact
- Attacks against thin clientsMediumImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist) or cloud infrastructure.
Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- 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
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty