Summer.fi
Summer.fi aims to be the most trusted entry point to deploy your capital into Decentralized Finance. You can now use it to borrow (generate) Dai and to Multiply the exposure to your favorite collateral assets, doing leverage-like trading.
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the 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 web/app bug reports and Critical/High/Medium severity smart contract bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. In addition, Critical/High severity bug reports must also come with a suggestion for a fix in order to be considered for a reward.
Previously highlighted vulnerabilities in the following security reviews are considered as out-of-scope:
- https://chainsecurity.com/wp-content/uploads/2021/09/ChainSecurity_Oazo_Apps_Limited_Multiply_Smart-Contract-audit_-September-7th-2021.pdf
- https://chainsecurity.com/wp-content/uploads/2021/10/ChainSecurity_Oazo_Apps_Limited_Multiply_FMM_extension_audit.pdf
- https://chainsecurity.com/security-audit/oasis-app-modular-proxy-actions/
The domain https://legacy.oasis.app/ and https://legacy.summer.fi/ is considered as out of scope of this program.
Summer.fi utilises third-party smart contracts and services (e.g. Maker Protocol, 1Inch, GUNI, etc.). The below rules apply to vulnerabilities in the underlying protocols and services:
- Only the smart contracts, websites and applications developed by the Summer.fi team are in the scope of this bug bounty program and are eligible for a reward.
- Vulnerabilities in the underlying protocols and services might be eligible for their dedicated bug bounty programs.
- The Summer.fi team will facilitate the communication related to the reported vulnerabilities in the underlying protocols and services.
At the moment the Summer.fi team is focusing on the new smart contract architecture, which utilizes actions within Operations to tie DeFi together.
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 10 000 for Critical smart contract bug reports, and a maximum reward of USD 100 000 for Critical smart contract bug reports.
Payouts are handled by the Summer.fi team directly and are denominated in USD. However, payouts are done in DAI.
Program Overview
Summer.fi aims to be the most trusted entry point to deploy your capital into Decentralized Finance. You can now use it to borrow (generate) Dai and to Multiply the exposure to your favorite collateral assets, doing leverage-like trading.
For more information about Summer.fi, please visit https://summer.fi/.
This bug bounty program is focused on their smart contracts, website and app and is focused on preventing:
- Any sort of loss of user funds, direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
- Permanent freezing of funds
- Causing any sort of economical damage to the smart contracts or the users (e.g. unbounded or unacceptable slippage)
- Protocol insolvency
- Unauthorized access resulting in the loss of funds
- Taking down the application/website permanently without the possibility of restoring it (Persistent)
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.