SushiSwap
SushiSwap is an automated market-making (AMM) decentralized exchange (DEX) that allows users to provide liquidity for token swaps.
PoC Required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$200,000Minimum reward to discourage security researchers from withholding a bug report:
$20,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
Theft of Yield vulnerability reports are temporarily not in scope for this bug bounty program, though this attack may be in the future.
All bug reports must come with a PoC. All bug reports without a PoC will not be accepted under this bug bounty program.
All critical payments for smart contracts are capped at 10% of economic damage.
Sushiswap is open to rewarding bounties beyond the critical cap for vulnerabilities with extreme impact.
Payouts are handled by the SushiSwap team directly and are denominated in USD. Payouts worth USD $100,000 and below are done in USDC. Payouts beyond USD $100,000 up to USD 200,000 are made in SUSHI, though the first $100,000 can be made in USDC if requested.
Program Overview
SushiSwap is an automated market-making (AMM) decentralized exchange (DEX) that allows users to provide liquidity for token swaps.
Further resources regarding SushiSwap can be found on their website, https://sushi.com.
Program focuses on three sets of contracts w/ majority of the contracts being built on top of BentoBox:
- SushiXSwap (Cross-chain swaps)
- Furo (Streams/Vesting contracts)
- Peripherals (Routers & Makers)
The bug bounty program is focused around it's smart contracts for the purpose of preventing the loss of user funds.
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
-
- Bug has not been publicly disclosed.
-
- Vulnerabilities that have been previously submitted by another contributor or already known by the SushiSwap development team are not eligible for rewards.
-
- Bugs must be reproducible in order for us to verify the vulnerability.
-
- Rewards and the validity of bugs are determined by the SushiSwap development team and any payouts are made at their sole discretion.
-
- Terms and conditions of the Bug Bounty program can be changed at any time at the discretion of SushiSwap.
- 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.