Uniwhale

Uniwhale is an oracle-based decentralized on-chain perpetual trading exchange where

• You can trade, with up to 200x leverage, BTC, ETH, and many mainstream crypto assets, directly from your wallet.
• You can provide liquidity with stablecoins like USDT, USDC, BUSD, and more, to earn real yield from market-making and leverage trading.

Based on objective price oracles and single-sided liquidity, Uniwhale aims to deliver the best trading experience for traders with zero credit risk and minimize impermanent loss for liquidity providers.

• Oracle-based price execution means zero slippage.
• Single-sided stablecoin liquidity means zero impermanent loss.
• Decentralized on-chain trading experience means zero credit risk.

For more information about Uniwhale, please visit https://uniwhale.co/

Responsible Publication

Uniwhale adheres to category 1. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.

Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.

Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale system with separate scales for Smart Contracts and Websites/Apps.

Rewards for critical smart contract bug reports will be further capped at 10% of direct funds at risk if the bug discovered is exploited. However, there is a minimum reward of USD 20 000.

Rewards for high smart contract bug reports will be further capped at 10% of direct funds at risk if the bug discovered is exploited. However, there is a minimum reward of USD 4 000.

Payouts and Payout Requirements:

Payouts are handled by the Uniwhale team directly and are denominated in USD. However, payouts are done in UNW. Uniwhale commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.

For the purposes of determining report validity, this is a Primacy of Impact program.

Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.

KYC Requirements:

Uniwhale does have a Know Your Customer (KYC) requirement for bug bounty payouts.

KYC Info Required:

• Identify Proof (Passport, / Driving License / National ID)

KYC information is only required on confirmation of the validity of a bug report.

Audit Discoveries and Known Issues:

Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.

Smart Contract

Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope.

Smart Contracts

• Smart Contracts - PoC, Smart Contract bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
• All smart contracts of Uniwhale can be found at: https://github.com/uniwhale-io/uniwhale-v1-contracts

Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.

Dev Environment and Documentation:

Uniwhale has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:

• https://github.com/uniwhale-io/uniwhale-v1-contracts

Impacts to other assets:

Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.

If whitehats can demonstrate a critical impact on code in production for an asset not in scope, Uniwhale encourages you to submit your bug report using the “primacy of impact exception” asset.

Impacts in Scope

(For Blockchain/DLT and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.

Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.

At Immunefi, we classify bugs on a simplified 5-level scale:

• Critical
• High
• Medium
• Low
• None

The following impacts and attack vectors are excluded from rewards by default for all Immunefi bug bounty programs:

• 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), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• Broken link hijacking is out of scope

Smart Contracts and Blockchain/DLT

• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Centralization risks

Prohibited Activities:

The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout.

Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.

Prohibited:

• Any testing with mainnet or public testnet deployed code; all testing should be done on private testnets
• 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
• Any other actions prohibited by the Immunefi Rules. These rules are subject to change at any time.