Scalable strategies onchain require best-in-class infrastructure to realize edge. Aera provides a platform from which a variety of strategies can be built.
PoC Required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$500,000Minimum reward to discourage security researchers from withholding a bug report:
$20,000Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope. The final classification however takes into consideration the likelihood of the impact being achieved based on the table. When submitting a bug report, select the original assigned impact level, but please be aware that its severity level may be reassigned based on the likelihood according to this table.
| Low Impact | Medium Impact | High Impact | |
|---|---|---|---|
| High Probability | MEDIUM | HIGH | CRITICAL |
| Medium Probability | LOW | MEDIUM | HIGH |
| Low Probability | LOW | LOW | MEDIUM |
In addition to Immunefi’s Vulnerability Severity Classification System, Gauntlet classifies vulnerabilities using the Common Vulnerability Scoring System (CVSS). In case of discrepancy, final determination is done by Gauntlet.
Repeatable Attack Limitations
In cases of repeatable attacks for smart contract bugs, only the first attack is considered if the smart contracts where the vulnerability exists can be upgraded, paused, or killed. If the attack impacts a smart contract directly holding funds that cannot be upgraded or paused, the amount of funds at risk will be calculated with the first attack being at 100% of the funds that could be stolen and then a reduction of 25% from the amount of the first attack for every 300 blocks the attack needs for subsequent attacks from the first attack, rounded down. For avoidance of doubt, if a second attack would happen at 600 blocks and then a third at 900 blocks, the funds at risk would be counted at 50% and 75% of the reward from the first attack, respectively.
Out of Scope
In addition to previously discovered bugs acknowledged in published audits or bug bounty competitions linked here, the following are out of scope:
- Risks of MEV in executed or submitted transactions
- Risks associated with an untrusted guardian, accountant or solver
- Risks associated with faulty oracles or third-party ERC20/ERC4626 asset implementations
- Risks associated with use of
executeby treasury - Risks associated with unsanctioned collusion of different roles (e.g., guardian and owner of asset registry)
Program Overview
Aera is a treasury management protocol that aims to address existing shortcomings with controlling treasury funds.
For more information about Aera, please visit https://www.aera.finance/.
Aera provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.
KYC Requirement
The provision of KYC is required to receive a reward for this bug bounty program where the following information will be required to be provided:
- Government-Issued ID or Corporate Charter Docs; EIN/TIN/ITIN or W9 (or equivalent);
- Proof of current address
KYC information is only required on confirmation of the validity of a bug report.
Primacy of Impact vs Primacy of Rules
Aera adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
Invoicing Information
If needed by the security researcher, Aera is able to provide the necessary information for the proper issuance of an invoice. This includes:
- Legal Entity
- Registered Address
- Email where to send the invoice
Audits
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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.