ImmuneFi Bug Bounty Program
ImmuneFi and Ease have been partners since early 2021, with the launch of the Armor Bug Bounty Alliance. ImmuneFi is the leading bug bounty platform, and Ease is pleased to partner with them again, by launching our own Bug Bounty Program for the Uninsurance ecosystem.
Bug Bounty programs are an integral part in allowing DeFi investors to truly feel at ease. This program launches prior to the launch of the app and the Uninsurance ecosystem, which is scheduled to go live April 13th.
The details of the program are below. If you think you have found a bug in any category level, please submit through official program page:
Rewards by threat level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. 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.
Critical USD 100 000
High USD 15 000
Medium USD 5 000
Low USD 1 000
All High and Critical Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
The following vulnerabilities are not eligible for a reward:
- All vulnerabilities marked in the security reviews are not eligible for a reward
- Reports about losses from governance attacks/off-chain exploits
- Griefing regarding capacity or capacity going over the limit
Payouts are handled by the Ease team directly and are denominated in USD. However, payouts are done in USDC.
Assets in Scope
If an impact can be caused to any other asset managed by Ease 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. This only applies to Critical impacts.
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.
- Theft or irredeemable freezing of user funds of more than 50% of the assets in any vault.
- Theft of funds or unsold yield of more than 1%, but less than 50% assets in any vault.
- Permanent freezing of unsold yield.
- Adapter for a protocol being broken to the point where it will not receive rewards that should be given.
- Theft or freezing of funds of less than 1% assets, but greater than a negligible amount.
- Non-privileged griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol).
- Adapters lacking the ability to get full normal rewards that the protocol returns (i.e. if the protocol gives 2 rewards tokens but the vault can only withdraw 1).
- Smart contract fails to deliver promised returns, but doesn’t lose more than a negligible amount of funds.
Particularly Vulnerable Areas:
- Decimal problems. We’re starting with Compound and a few USDC contracts that require normalization so we must prevent any problems as this would likely lead to a critical.
- Protocol composability problems. Each shield adapter functions differently and there could be high or critical severity problems here.
- Conversion rates. On mint/redeem if our calculations are off this could easily lead to criticals.
- Merkle trees for pricing or liquidation amounts being able to be manipulated in some way.
In case of discrepancy between Immunefi Vulnerability Severity Classification System V2 and Ease’s classification above, Ease’s classification will be followed.
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)
Smart Contracts and 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
- Arbitrage tricks (not complete attacks but ways for arbitrageurs to get extra funds, such as depositing funds into a shield then buying rewards themselves)
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