Wombat Exchange
The Wombat Team has created an algorithm that redefines the stable swap experience, bringing greater capital efficiency to fuel DeFi growth and adoption.
PoC required
KYC 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 and all Critical 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.
All issues previously highlighted in the following audit reports are considered out of scope:
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.
Critical website and application bug reports will be rewarded with USD 10 000 only if the impact leads to a direct loss in funds. All other impacts that would be classified as Critical would be rewarded no more than USD 2 000.
Payouts are handled by the Wombat Exchange team directly and are denominated in USD. However, payouts are done in USDC or USDT, at the discretion of the team.
Program Overview
The Wombat Team has created an algorithm that redefines the stable swap experience, bringing greater capital efficiency to fuel DeFi growth and adoption.
Maximize Capital Utilization by Removing Liquidity Silos
- Open-liquidity pools to achieve higher capital utilization
- Allows single token liquidity provisions instead of pools-based
- No impermanent loss
More User-Friendly and Removing Barriers to Scalability
- Innovative coverage-ratio-based stableswap mechanism to remove scalability barriers
- Single-token LP token
- Simple to calculate the underlying
- Each stablecoins has their own equilibrium
- Great for yield farming, borrowing and lending platforms and trading platforms
For more information about Wombat Exchange, please visit https://www.wombat.exchange/.
KYC Requirements
All whitehats are required to submit identification and proof of address for payment.
KYC required
The submission of KYC information is a requirement 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.