EXCEPT the folders “external/aave”, “mocks”, and “test”.

All smart contracts of Alchemix can be found at [https://github.com/alchemix-finance/v2-foundry](https://github.com/alchemix-finance/v2-foundry). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.  The in scope contracts can be found in the “src” folder, [https://github.com/alchemix-finance/v2-foundry/tree/master/src](https://github.com/alchemix-finance/v2-foundry/tree/master/src), but excludes the “external/aave”, “mocks”, and “test” folder. All 3rd party code in any folder is also out of scope.

Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target. 

If an impact can be caused to any other asset managed by Alchemix that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to Critical and High impacts.

Alchemix Finance is a future-yield-backed synthetic asset platform and community DAO. The platform gives you advances on your yield farming via a synthetic token that represents a fungible claim on underlying collateral in the Alchemix protocol. 

Smart contract fails to deliver promised returns, but doesn’t lose value

Unbounded gas consumption, that does not cause a more severe bug

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for at least 1 day

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Smart contract unable to operate due to lack of token funds

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Unbounded gas consumption

Miner-extractable value (MEV)

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

Permanent freezing of funds

Protocol insolvency

Alchemix Codebase

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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 bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All Medium, High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Low Smart Contract bug reports require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical smart contract vulnerabilities are capped at __10%__ of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of __USD 35 000__ and a maximum of __USD 300 000__. For High vulnerability reports, the payouts will be primarily calculated as 10% of potential economic damage, primarily taking into account funds at risk but also PR and branding aspects, and bounded by the payout range for the vulnerability level. 

The following vulnerabilities are not eligible for a reward:

  - All vulnerabilities listed here [https://github.com/code-423n4/2022-05-alchemix-findings/issues?q=is%3Aopen+is%3Aissue++-label%3A%22G+%28Gas+Optimization%29%22+-label%3A%22QA+%28Quality+Assurance%29%22 ](https://github.com/code-423n4/2022-05-alchemix-findings/issues?q=is%3Aopen+is%3Aissue++-label%3A%22G+%28Gas+Optimization%29%22+-label%3A%22QA+%28Quality+Assurance%29%22)(succinct) 
  - All vulnerabilities listed here [https://github.com/code-423n4/2022-05-alchemix-findings/issues?q=is%3Aopen+is%3Aissue+](https://github.com/code-423n4/2022-05-alchemix-findings/issues?q=is%3Aopen+is%3Aissue+) (full)
  - All vulnerabilities listed in [Runtime Verification audit](https://github.com/runtimeverification/publications/blob/main/reports/smart-contracts/Alchemix_v2.pdf)

Payouts are handled by the __Alchemix__ team directly and are denominated in USD. However, payouts are done in __ALCX__.