Cardano Foundation
Bounty Range
$1,000 - $10,000
external program
Cardano Foundation
Bounty Range
$1,000 - $10,000
external program
The Cardano Foundation is tasked with advancing the public digital infrastructure Cardano, working to anchor it as a utility for financial and social systems.
The Cardano Foundation is tasked with advancing the public digital infrastructure Cardano, working to anchor it as a utility for financial and social systems. We develop infrastructure tooling—including where there may not be an immediate commercial use case—plus strengthen operational resilience, and drive diversity of on-infrastructure use cases as well as the development of sound and representative governance.
For more information about The Cardano Foundation, please visit https://cardanofoundation.org/
The Cardano Foundation provides rewards in fiat USD.
Websites and Applications
Payouts are handled by the Cardano Foundation team directly and are denominated in USD. However, payments are done in fiat USD via Bank Transfer. This bug bounty program will also have a hard cap of USD 100,000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis. All remaining valid reports will have their rewards considered on a case by case basis.
The Cardano Foundation adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
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.
No KYC information is required for payout processing.
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.
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: