Aevo
Aevo is a new protocol that creates crypto structured products for DeFi. Structured products are packaged financial instruments that use a combination of derivatives to achieve some specific risk-return objective, such as betting on volatility, enhancing yields or principal protection.
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
Smart Contracts Critical:
- Loss of user funds:
- 1% of all assets at risk, minimum 50 000 USD, maximum 300 000 USD
- Loss of non-user funds (e.g. treasury):
- 1% of assets at risk, minimum 50 000 USD , maximum 150 000 USD
Smart Contracts High:
- 1% of all assets at risk when attack persists for 1 month minimum 10 000 USD, maximum of 50 000 USD
Smart Contracts Medium:
- 1% of all assets at risk when attack persists for 1 month minimum 5 000 USD, maximum 25 000 USD
Smart Contracts Low:
- 2 000 USD
Payouts are handled by the Aevo team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
Aevo is a new protocol that creates crypto structured products for DeFi. Structured products are packaged financial instruments that use a combination of derivatives to achieve some specific risk-return objective, such as betting on volatility, enhancing yields or principal protection.
One of its products, Theta Vault, is a yield-focused strategy on ETH and WBTC. The first Theta Vault will run a covered call strategy, which earns yield on a weekly basis through writing out of the money covered calls and collecting the premiums.
The bug bounty program is focused around its smart contracts and is mostly concerned with the loss of user funds.
For more information about Aevo, please visit https://aevo.xyz
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.