- Top reward
- $300,000
- Top severity paid
- Critical
- Assets in scope
- 3
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $300,000
- for critical bugs, from $1,000.
- Report on Immunefi
- Submit through the program page.
- Paid by USDC
- No identity check to get paid.
- No public write-ups
- Keep findings private.
Rewards
What Immunefi lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$300,000 from $50,000 |
| High |
|
$50,000 from $10,000 |
| Medium |
|
$25,000 from $5,000 |
| Low |
|
$1,000 |
Scope
3 assets you may test.
Smart contracts 2
- https://arbiscan.io/address/0x80d40e32fad8be8da5c6a42b8af1e181984d137c
- https://etherscan.io/address/0x4082C9647c098a6493fb499EaE63b5ce3259c574
Source code 1
- Smart Contracts
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Aevo (via Immunefi)'s policy. "We" in these lines means the program, not this site.
While testing
-
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
-
Proof of concept is always required for all severities.
Summarised with AI from the program policy on Immunefi, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 55 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from immunefi.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Back to Explore 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. Avalanche BSC ETH Solana Defi Derivatives Yield Aggregator Solidity Maximum Bounty $300,000 Live Since 12 April 2021 Last Updated 23 July 2026 PoC Required Submit a Bug Information Scope Resources Rewards Aevo provides rewards in USDC , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $300,000 Min: $50,000 Primacy of Rules High Max: $50,000 Min: $10,000 Primacy of Rules Medium Max: $25,000 Min: $5,000 Primacy of Rules Low Flat: $1,000 Primacy of Rules Rewards Body 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 . View impacts in scope 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. 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. Proof of Concept Proof of concept is always required for all severities. Prohibited Activities Default 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 2