yelay.io
Yelay is permissionless and non-custodial middleware that allows banks, fintech, funds, exchanges, custodians, treasuries, launchpools and other builders to earn DeFi returns in a fully composable manner.
PoC Required
KYC 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
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Temporary freezing of funds for more than 24 hours
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Unbounded gas consumption
Contract fails to deliver promised returns, but doesn't lose direct monetary value. F.e. loss of points, sYLAY balance, wrong yield or APY calculation etc.
Out of scope
- Impacts relying on the intended wrongdoing of protocol admins having privileged access to the key functions of the protocol
- Impacts where protocol functionality works as designed (f.e. “Users do not receive yield” in the Launchpool version of Yelay V3, or “Yield has been temporarily not generated due to the lack of triggering events”
- Specifics of the ‘Deposit lock’ feature: “In case of DepositLock, Yield data is calculated offchain. If Client has set up DepositLock functionality only deposits into projectId through that are considered 'yield accruing'. If some user decides to bypass the DepositLockPlugin and deposit directly into the Vault using the same projectId - users will not receive any rewards. Such users are simply filtered out from offchain yield calculations.”
- Use of malicious strategies or those which are not fit for the purpose. For example, strategies which incur deposit/withdrawal/management fees. Only performance fee is allowed for strategies used on Yelay V3 vaults.
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