Alchemix
Alchemix is your unified platform for saving, earning, borrowing, and fixed-term fixed-yield opportunities—all in one place. Built on years of iteration since launching the original self-repaying loan in 2021, Alchemix v3 brings all three pillars together with a smarter, more flexible design. The protocol allows you to:
- Save and grow – deposit ETH or USDC and let our vault invest and earn yield across diversified strategies.
- Borrow up to 90% LTV – access liquidity now while your collateral grows with yield and your leverage is reduced over time through scheduled redemptions. No interest rates to monitor, no price-based liquidations.
- Earn fixed-rate yield – lock in predictable returns through fixed-term redemptions of alETH or alUSD.
Triaged by Immunefi
PoC Required
Vault program
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Protocol insolvency
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Temporary freezing of funds for at least 1 day
Miner-extractable value (MEV)
Smart contract fails to deliver promised returns, but doesn’t lose value
Unbounded gas consumption, that does not cause a more severe bug
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