All code of Aera can be found at [https://github.com/aera-finance/aera-contracts-public/tree/main/v2.](https://github.com/aera-finance/aera-contracts-public/tree/main/v2) Documentation for the assets provided in the table can be found at [https://docs.aera.finance/. ](https://docs.aera.finance/) 

Other helpful links include:
- [https://uploads-ssl.webflow.com/62cd150e5e9efc960319c44d/6346c4525380f8fa6435c2b5_Aera_Whitepaper.pdf](https://uploads-ssl.webflow.com/62cd150e5e9efc960319c44d/6346c4525380f8fa6435c2b5_Aera_Whitepaper.pdf)

Aera is a treasury management protocol that aims to address existing shortcomings with controlling treasury funds.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 180,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 2,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.   

__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.

__Restrictions on Security Researcher Eligibility__

Security researchers who fall under any of the following are ineligible for a reward
- Bug reports from current or prior compensated team members of Gauntlet Networks Inc. or Aera Foundation will not be eligible for a reward.
- Employees and team members of third-party suppliers to Gauntlet Networks Inc. or Aera Foundation will also not be eligible for a reward.
- Bug reports from OpenZeppelin team members and other third-party protocols that are used as Aera assets in the asset registry (including but not limited to Compound, Aave and others) are also not eligible for the bug bounty program (as they are considered critical infrastructure for Aera)
- The submitter will also need to: be at least 18 years of age, be reporting in an individual capacity, or if employed by a company, reporting with the company’s written approval to submit a disclosure to Gauntlet Networks Inc. Not be subject to US sanctions or reside in a US-embargoed country.

__Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. 
- Risks of MEV in executed or submitted transactions
- Risks associated with an untrusted guardian
- Risks associated with faulty oracles or third-party ERC20/ERC4626 asset implementations
- Risks associated with use of `execute` by treasury
- Risks associated with unsanctioned collusion of different roles (e.g., guardian and owner of asset registry)

__Previous Audits__

Aera has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://github.com/aera-finance/aera-contracts-public/blob/main/v2/audits/spearbit/2023-09-22.pdf ](https://github.com/aera-finance/aera-contracts-public/blob/main/v2/audits/spearbit/2023-09-22.pdf)

__Feasibility Limitations__

Bug reports that require an attack that involve one or more other protocols (e.g. utilizing flash loans from a margin protocol or manipulating the spot prices on a DEX), either to make an attack more severe than it would be in isolation, or to achieve an attack that would otherwise be impossible or infeasible, would be -50% of bounty reward. However, they will be considered as in-scope and categorized according to the program rules as long as all of the following are true:
- Losses or other negative effects of the attack are inflicted upon Aera ecosystem participants 
- The additional protocols used must have enough liquidity in various assets to allow the attack to succeed at the time of bug report submission. For example: if an attack requires an ETH flash loan, but the amount is larger than all the ETH available for loan across the ecosystem

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract, Critical Severity Level

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the Aera team directly and are denominated in USD. However, payments are done in USDC.

Aera

Resources & Documentation