PoC Required
Rewards
Rewards by Threat Level
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$100,000Rewards 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 is 100,000 USD. For high Blockchain/DLT bugs, the reward is 10,000 USD. For medium Blockchain/DLT bugs, the reward is 5,000 USD. For low Blockchain/DLT bugs, the reward is 1,000 USD.
Reward Payment Terms
Payouts are handled by Power Up Privacy directly and are denominated in USD. However, payments are done in XMR on Monero
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Program Overview
monero-oxide is a collection of Rust libraries to work with the Monero protocol, including its zero-knowledge proofs. monero-oxide hosts a monero-wallet, a memory-safe library to build and sign Monero transactions, including an implementation of the FROSTLASS threshold signing protocol. monero-oxide is used by Serai (https://serai.exchange) and Cuprate (https://cuprate.org). For bugs affecting Serai, which hosts its own bug bounty program on Immunefi (https://immunefi.com/bounty/serai), both programs should be submitted to yet only one will issue a reward (of the submitter’s choice).
For more information about monero-oxide, please visit https://github.com/monero-oxide/monero-oxide
monero-oxide provides rewards in [XMR] on [Monero], denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
All submissions will be reviewed with debug-assertions = false and overflow-checks = true.
Eligibility Criteria
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
- Be a member of the monero-oxide, Cuprate, or Serai organizations
- Have written code required for the submission to be eligible
- Security auditors that directly or indirectly participated in the audit review
Responsible Publication
monero-oxide adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
monero-oxide adheres to the Primacy of Impact for the following impacts:
- Blockchain/DLT - Critical
- Blockchain/DLT - High
- Blockchain/DLT - Medium
- Blockchain/DLT - Low
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. For more information, please see Best Practices: Primacy of Impact
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.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs (listed below) 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.
- https://github.com/monero-oxide/monero-oxide/issues
- https://github.com/Cuprate/cuprate/issues
- https://github.com/serai-dex/serai/issues
Previous Audits
monero-oxide’s completed audit reports can be found at https://github.com/monero-oxide/monero-oxide/tree/main/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward without demonstrated remaining impact.
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.
Audits
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.