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.
PoC Required
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
Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
Permanent freezing of funds
Permanent freezing of NFTs
Unauthorized minting of NFTs
Protocol insolvency
Temproary Freezing of Funds at 0 cost or profit to attacker for greater than 1 day
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Griefing at minimal no to cost to attacker
Miner Extractable Value in excess of 0.75%
Smart contract unable to operate due to lack of token funds
Out of scope
Yield Strategies Alchemix v3 is set to go live on 4/13 based on primacy of impact, at which point for yield strategies to be in scope they must be deployed and tied into the MYT. Prior to deployment, only the following yield strategies are in scope:
Mainnet USDC - EulerUSD, TokeAutoUSD Mainnet wETH - EulerwETH, TokeAutoETH, WstETH Arbitrum - AaveUSDC, EulerUSDc, FluidUSDC Arbitrum - aaveETH, EulerETH OP - AaveUSDC OP - no wETH strats
The following strategies are out of scope prior to deployment: Mainnet EtherFiEETH, Mainnet siUSD, Mainnet FraxETH, Optimism wstETH
Trusted Admin Admin, Curator, Allocator, and Sentinel are all trusted roles. This will change in the future with onchain governance, but for now are assumed trusted. As an example, strategies recieve a high/med/low risk rating, which dictates maximum relative caps. However, these relative caps are not yet enforced onchain and instead are enforced by trusted curators/allocators.
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