Ease
Submit a BugProgram Overview
Ease wants to make DeFi as easy and safe as possible. We aim to cover every dollar in DeFi so that users can finally feel at ease. The core members of the ease team have been around for a long time. Some of us already worked with David Chaum on DigiCash/eCash many eons ago. Others made the first NFT derivatives. All of us have been interested in blockchain technology and its societal impact for many years.
For more information about Ease, please visit https://ease.org/.
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 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.
Smart Contract
- Critical
- Level
- USD $100,000
- Payout
- High
- Level
- USD $15,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - BribePotType
- Smart Contract - DelegableType
- Smart Contract - EaseTokenType
- Smart Contract - GvTokenType
- Smart Contract - TokenSwapType
- TargetSmart Contract - GovernorBravoDelegateType
- TargetSmart Contract - GovernorBravoDelegatorType
- Smart Contract - RcaShieldAaveType
- TargetSmart Contract - RcaShieldCompoundType
- Smart Contract - RcaShieldConvexType
- Smart Contract - RcaShieldOnsenType
- Smart Contract - RcaControllerType
- Smart Contract - RcaShieldType
- Smart Contract - RcaShieldBaseType
- Smart Contract - RcaShieldNormalizedType
- Smart Contract - RcaTreasuryType
- Smart Contract - AaveType
- Smart Contract - CompoundType
- Smart Contract - ConvexType
- Smart Contract - NexusMutualType
- Smart Contract - SushiswapType
- Smart Contract - GovernableType
- Smart Contract - RcaGovernableType
- Smart Contract - RcaControllerType
- Smart Contract - RcaShieldType
- Smart Contract - IRouterType
- Smart Contract - MerkleProofType
- TargetSmart Contract - GovernorBravoInterfacesType
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.
Smart Contract
- Theft or irredeemable freezing of user funds of more than 50% of the assets in any vault.CriticalImpact
- Theft of funds or unsold yield of more than 1%, but less than 50% assets in any vaultHighImpact
- Permanent freezing of unsold yieldHighImpact
- Adapter for a protocol being broken to the point where it will not receive rewards that should be givenHighImpact
- Theft or freezing of funds of less than 1% assets, but greater than a negligible amountMediumImpact
- Non-privileged griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- 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)MediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose more than a negligible amount of fundsLowImpact
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