WOOFi
WOOFi is a unique decentralized exchange that bridges the deep liquidity of centralized exchanges on chain. This enables DeFi traders to swap with size and maximize their profits through the lowest swap fee and minimal slippage.
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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All bug reports must come with a PoC and a suggestion for a fix in order to be considered for a reward.
All known issues previously highlighted in the past audit reports are considered to be out-of-scope
Payouts are handled by the WOOFi team directly and are denominated in USD. However, payouts are done in WOO.
Program Overview
WOOFi is a unique decentralized exchange that bridges the deep liquidity of centralized exchanges on chain. This enables DeFi traders to swap with size and maximize their profits through the lowest swap fee and minimal slippage.
In addition to this, WOOFi has four other core components: Cross-chain swaps - Move any asset quickly and seamlessly across 10 supported chains with minimum slippage Revenue sharing - Stake WOO tokens and earn 80% of all protocol fees in WOO or USDC Supercharged yields - Lend assets to WOOFi's liquidity manager and earn leading single-sided yield, free of impermanent loss Perpetual futures - Trade perpetual futures with WOOFi Pro's order book, enjoy the CeFi trading experience while keeping self-custody
For more information about WOOFi, please visit https://fi.woo.org/
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
- Theft of governance funds
- Economic exploits
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.