Alchemix
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.
PoC required
Vault program
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
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)
Smart contract fails to deliver promised returns, but doesn’t lose value
Out of scope
- Best practice critiques
- Specifically for the crosschaincanonicalbase.sol contract: This contract is outdated bridging code for Layer 2 alAssets, however, the layer 2 alAssets were upgraded and still contain state variables related to this code, therefore the code has not been stripped from the Layer 2 alAssets. The crosschaincanonicalbase.sol contract is out of scope, EXCEPT for any bugs that would allow anyone besides a trusted admin/multisig to access the functions, or any issues with the current implementation of the bridge/L2 token (alchemicalTokenBase) created by this contract.
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers
205.4k