Oasis
Bounty Range
$1,000 - $100,000
external program
Oasis
Oasis is a privacy layer for Web3 with native high performance and cross-chain interoperability.
Blockchain: L1
Maximum Bounty: $100,000
Live Since: 20 February 2024
Last Updated: 24 January 2025
Requirements:
Oasis provides rewards in USDC on Ethereum, denominated in USD.
Blockchain/DLT
Critical
High
Medium
Critical Reward Calculation
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of $100,000.
Minimum reward to discourage security researchers from withholding a bug report: $10,000
The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted.
Websites and Applications
Critical
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward USD 100,000. However, a minimum reward of USD 10,000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows:
Network not being able to confirm new transactions (total network shutdown and does not include network level DDoS attack): USD 10,000
Unintended permanent chain split requiring hard fork (network partition requiring hard fork): USD 10,000
Permanent freezing of funds (fix requires hardfork): USD 10,000
Reward Payment Terms
Payouts are handled by the Oasis team directly and are denominated in USD. However, payments are done in USDC.
Oasis is a privacy layer for Web3 with native high performance and cross-chain interoperability.
For more information about Oasis, please visit https://oasisprotocol.org/
Oasis provides rewards in USDC, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
Oasis will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Oasis adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Bug reports covering previously-discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk. Github issues can be found here: https://github.com/oasisprotocol
By adhering to Immunefi's best practice recommendations, Oasis has satisfied the requirements for the Immunefi Standard Badge.
Participants must adhere to the Eligibility Criteria.
The submission of KYC information is a requirement for payout processing.
Proof of concept is always required for all severities.
Category 3: Approval Required
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.