
Aleo
Bounty Range
$5,000 - $65,000
external program
Aleo is a developer platform that uses zero-knowledge technology to enable decentralized apps that are private, programmable, secure, and scalable. We are launching a fully permissionless, next-generation blockchain & new consensus protocol that is faster, more efficient, and more decentralized than traditional models. Aleo is more than a blockchain. It's a new computing paradigm defined by client-side execution & cutting-edge cryptography designed for the web.
For more information about Aleo, please visit https://aleo.org/
Aleo provides rewards in ALEO on Aleo Network, denominated in USD.
Blockchain/DLT
Critical
High
For Critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward of $65,000. However, a minimum reward of $10,000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
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.
For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows:
For High Blockchain/DLT non-funds-at risk impacts, the reward will be paid out as follows:
Payouts are handled by the Aleo team directly and are denominated in USD. However, payments are done in ALEO on Aleo Network.
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.
Aleo will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
Aleo adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.
Aleo 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.
Aleo's completed audit reports can be found at https://aleo.org/post/aleo-completes-security-audits-of-snarkos-and-snarkvm/. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
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 feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.