Swaylend is a leading lending protocol on the Fuel network, based on a fork of Compound V3.
For more information, visit: https://swaylend.com/
IOP | Swaylend Frontend focuses on Web2 attack vectors. Please review the in-scope impacts.
Swaylend rewards are provided in USDC, denominated in USD.
Evaluating
Triaged by Immunefi
PoC required
This Audit Competition Is Under Evaluation
Rewards
Rewards by Threat Level
The following reward terms are a summary, for the full details read our IOP | SwayLend: Frontend - Reward Distribution Terms.
A reward pool of $30,000 USD will be distributed among participants, even if no valid bugs are found.
Duplicates and private known issues are valid for a reward.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.
Insight Rewards Payment Terms
Insight Rewards: Portion of the Rewards Pool
*The "Insight" severity was introduced on Audit Competition & Attackathon programs to recognize contributions that extend beyond identifying immediate vulnerabilities. Currently, it's not an option to select the Insight severity when submitting a report. However, our team or program will designate it accordingly if applicable. "Insights" underscores our commitment to valuing all types of contributions that contribute to a more secure environment and will always be rewarded. View more information about Insights
Duplicates of Insight are not rewarded.
Program Overview
Swaylend is a leading lending protocol on the Fuel network. It is a fork of Compound V3.
For more information about Swaylend, please visit https://swaylend.com/
Swaylend provides rewards in UDSC, denominated in USD.
Audits
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
- 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