monero-oxide
Bounty Range
$1,000 - $100,000
external program
monero-oxide
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, 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.
Blockchain/DLT
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
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.
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
monero-oxide adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
monero-oxide 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. Proof of concept is always required for all severities.
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.
Known issues can be found at:
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.
| Auditor | Link | Completed at |
|---|---|---|
| Cypher Stack | https://github.com/monero-oxide/monero-oxide/tree/main/audits/Cypher%20Stack%20May%202025 | 14 August 2025 |
No KYC information is required for payout processing.
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.
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, including standards for: