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.

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.

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:

• https://docs.wombat.exchange/resources/security-audits

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.

All smart contracts of Wombat Exchange can be found at https://github.com/wombat-exchange/v1-core. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If a Critical or High severity impact can be caused to any other asset managed by Wombat Exchange that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices
• Vulnerabilities primarily caused by browser/plugin defects
• Any vulnerability exploit requiring CSP bypass resulting from a browser bug

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• 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
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty