Swell
Swell is a permissionless, non-custodial, and liquid ETH staking protocol that is built for stakers, node operators, and the Ethereum ecosystem.
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 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.
Rewards for critical smart contract vulnerabilities are further capped at 10% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 50 000 and a maximum reward of USD 250 000 for Critical smart contract bug reports.
Previously known issues highlighted in the following audit reports are considered as out of scope:
Payouts are handled by the Swell team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
Swell is a permissionless, non-custodial, and liquid ETH staking protocol that is built for stakers, node operators, and the Ethereum ecosystem.
Swell provides users with an opportunity to earn yield on the ETH they hold through staking. This is done by staking ETH in conjunction with node operators that participate in validating the Ethereum proof-of-stake blockchain. The yield is earned through staking rewards received from the blockchain for validating block production.
Above all Swell aims to contribute to the Ethereum ecosystem and it’s users by simplifying the staking process as much as possible and driving utility for the reward-bearing token swETH.
For more information about Swell, please visit https://swellnetwork.io/.
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.